Laugh if you must, please help if you can.
Mt2-L03
Situation is this I was running Pac 9/5 and want to upgrade, well after several failed attempts I saw newer Pac roms need 322 base. So I said well I have flashed so many times piece of cake. Well I flash recovery and then run 322 up grade and low and behold phone boots!
Well here is the punchline 322 boots to smartcover screen only!!!! I can not get into phone No problem I will upgrade twrp :fingers-crossed: oops 322 developer mode disabled! no ADB for me :crying: So no smart cover but in smartcoverlock screen it will not open.
Suggestions?
TIA
UPDATE: downgraded to ICS (sorry) thought cool as smart cover never worked in that. Well woops it sure does now. WTF Buy a smart cover from EBAY I guess. Hope that works!!!!
I am not sure how it got turned on but I can't flash anything but stock as no developer options enabled
oncouch1 said:
Laugh if you must, please help if you can.
Situation is this I was running Pac 9/5 and want to upgrade, well after several failed attempts I saw newer Pac roms need 322 base. So I said well I have flashed so many times piece of cake. Well I flash recovery and then run 322 up grade and low and behold phone boots!
Well here is the punchline 322 boots to smartcover screen only!!!! I can not get into phone No problem I will upgrade twrp :fingers-crossed: oops 322 developer mode disabled! no ADB for me :crying: So no smart cover but in smartcoverlock screen it will not open.
Suggestions?
TIA
UPDATE: downgraded to kk thought cool as smart cover never worked in that. Well woops it sure does now. WTF Buy a smart cover from EBAY I guess. Hope that works!!!!
Click to expand...
Click to collapse
Not sure about your issue. Maybe try to upgrade to B322 again?
BTW, Smart cover won't work on PAC-ROM or CM.
Edited: I meant you won't see anything other than clock from the smart cover window.
oncouch1 said:
Laugh if you must, please help if you can.
Situation is this I was running Pac 9/5 and want to upgrade, well after several failed attempts I saw newer Pac roms need 322 base. So I said well I have flashed so many times piece of cake. Well I flash recovery and then run 322 up grade and low and behold phone boots!
Well here is the punchline 322 boots to smartcover screen only!!!! I can not get into phone No problem I will upgrade twrp :fingers-crossed: oops 322 developer mode disabled! no ADB for me :crying: So no smart cover but in smartcoverlock screen it will not open.
Suggestions?
TIA
UPDATE: downgraded to kk thought cool as smart cover never worked in that. Well woops it sure does now. WTF Buy a smart cover from EBAY I guess. Hope that works!!!!
Click to expand...
Click to collapse
Which phone do you have. 322 was for mt2-l03. No KK for this phone.
Moody66 said:
Which phone do you have. 322 was for mt2-l03. No KK for this phone.
Click to expand...
Click to collapse
I thought that's a typo.
MT2-User said:
I thought that's a typo.
Click to expand...
Click to collapse
Ya. Confusing. Afraid to try and help until I understand. Lol
MT2-User said:
I thought that's a typo.
Click to expand...
Click to collapse
my error again!
oncouch1 said:
my error again!
Click to expand...
Click to collapse
To turn on developer options open settings... Select about phone... Tap on build number 10 times. Then back to settings and it will be available. BTW I do believe you can get snqrt cover working by using an xposed module with CM or PAC.
Moody66 said:
To turn on developer options open settings... Select about phone... Tap on build number 10 times. Then back to settings and it will be available. BTW I do believe you can get snqrt cover working by using an xposed module with CM or PAC.
Click to expand...
Click to collapse
The rub is I have no smart cover, the phone is just acting like it. I cannot open lock screen. I have the small clock showing. I tried calling it but rather than showing the symbols to unlock it goes to voicemail.
oncouch1 said:
The rub is I have no smart cover, the phone is just acting like it. I cannot open lock screen. I have the small clock showing. I tried calling it but rather than showing the symbols to unlock it goes to voicemail.
Click to expand...
Click to collapse
Hmmm. Could be actually damaged. Flash cm or PAC and see how it does.
Moody66 said:
Hmmm. Could be actually damaged. Flash cm or PAC and see how it does.
Click to expand...
Click to collapse
Thanks but I only have stock recovery and cannot adb as developer mode.l not enabled.
Guess I proved you can brick these afterall .
If the computer is still able to see your phone and or SD when you connect it you may want to try copying the b322 update to your SD card and reflash B322. As far as I know the phone should still allow you to transfer files to it without having ADB enabled. If not then I don't know what else to do.
oncouch1 said:
Thanks but I only have stock recovery and cannot adb as developer mode.l not enabled.
Guess I proved you can brick these afterall .
Click to expand...
Click to collapse
No it's not bricked.. Just boot TWRP from your PC and flash whatever you want. And twrp.. Fastboot. I will find a link. Thanks superbass.https://m.youtube.com/watch?v=sjA4F_TzzwQ
oncouch1 said:
Thanks but I only have stock recovery and cannot adb as developer mode.l not enabled.
Guess I proved you can brick these afterall .
Click to expand...
Click to collapse
You don't need to have ADB enabled for commands to work in fatsboot. So you can still flash TRWP.
I would just do the triple button method before you install TWRP, let stock recovery wipe and reflash the stock 322 build and see where you're at.
OK, how do I buy you guys a beer? I am back up and running pac rom. I followed moody's link and flashed twrp. Thank you so much!
This community rules!!!!!
oncouch1 said:
OK, how do I buy you guys a beer? I am back up and running pac rom. I followed moody's link and flashed twrp. Thank you so much!
This community rules!!!!!
Click to expand...
Click to collapse
Glad to hear it! Hopefully someone else that has that issue will find this useful!
I think it ended up being a DPI issue as I always use 240. When I tried to load 322 again same thing, both attempts I was running PAC at 240.
Thanks again.
ok so after getting backup and running pac rom for months. I tried to go back to stock b322. I still end up with the lockscreen like i set smartcover and cant unlock. I was thinking resolution but I left it stock. Any suggestions on how to try and get stock lollipop?
BTW: I bought a smart cover and of coars e it didn't work.
Related
http://shipped-roms.com/shipped/Desi...ith_driver.exe
Tried running that .exe and it works for a bit and then says it can't connect to my phone. Then I'm stuck at "htc" and I have to pull the battery and when I reboot everything's screwed up but ti's still CM6.
going to flash the pb00img.zip in this topic
http://forum.xda-developers.com/showthread.php?t=641588&highlight=unroot
Hungry Man said:
http://shipped-roms.com/shipped/Desi...ith_driver.exe
Tried running that .exe and it works for a bit and then says it can't connect to my phone. Then I'm stuck at "htc" and I have to pull the battery and when I reboot everything's screwed up but ti's still CM6.
going to flash the pb00img.zip in this topic
http://forum.xda-developers.com/showthread.php?t=641588&highlight=unroot
Click to expand...
Click to collapse
That's weird. Careful you get the right version of PB00IMG. The one at the top of that thread is leak v1, not leak v3. Anyway, if you're still having trouble un-rooting, you might have to do it the old-fashioned way: un-root to 1.5 following the original "downgrade" instructions, and then upgrade to 2.1 by putting the OTA zip (renamed to update.zip) onto your SD card.
Yeah I may do that. I'm using the "patched version."
Hungry Man said:
Yeah I may do that. I'm using the "patched version."
Click to expand...
Click to collapse
That's v1. Don't do that. I can't find v3 here on XDA, so search android forums for it instead. I'm pretty sure it's on the first or second page because there have been recent references to it.
Hungry Man said:
http://shipped-roms.com/shipped/Desi...ith_driver.exe
Tried running that .exe and it works for a bit and then says it can't connect to my phone. Then I'm stuck at "htc" and I have to pull the battery and when I reboot everything's screwed up but ti's still CM6.
going to flash the pb00img.zip in this topic
http://forum.xda-developers.com/showthread.php?t=641588&highlight=unroot
Click to expand...
Click to collapse
hope things work out for you bro
Too late for today anyway, I'll have to do it tomorrow =\
Hungry Man said:
Too late for today anyway, I'll have to do it tomorrow =\
Click to expand...
Click to collapse
I got you hungry man this is what i did so i was able to send back my broken phone
go here and download PB00IMG 2.1 official.zip the one where its says you lose root its the old 2.1 leak http://android.grdlock.net//index.php?&direction=0&order=&directory=PB00IMG Roms and rename it to the PB00IMG.
put it on root of the sd n im sure u know the rest
turn on phone using send and power and follow the prompt
this game me 1.49 s-on
stock recovery
and maybe a leaked rom i didnt check
send my oringial out now thank god i found this today
Thanks. I'll be trying tomorrow, don't want to go very long without root if I can help it =p
It says "Can't open /sdcard/pb00img.zip (bad)"
wtf am I doing wrong -.-
nevermind, using fastboot lol I'm dumb >_> it's working now
Hungry Man said:
nevermind, using fastboot lol I'm dumb >_> it's working now
Click to expand...
Click to collapse
its not perfect but at least its good enough to send back
as long as the correct boot loader is there
so how is the progress
I seem to have managed. I'm trying to make it look normal lmao installing custom launcher and some random apps.
wait why are you un-rooting?
Trackball's killing me, I'm going to return it for a new eris.
Hungry Man said:
Trackball's killing me, I'm going to return it for a new eris.
Click to expand...
Click to collapse
hmm but your still going to do a wipe before you send off
i totally screwed mine up cause i left a custom bootscreen but my hacking computer is being repaired
Worked perfectly. Went to Verizon and they'll get my phone to me in two days.
hungry man said:
worked perfectly. Went to verizon and they'll get my phone to me in two days.
Click to expand...
Click to collapse
glad it worked out bro
DS36 said:
hmm but your still going to do a wipe before you send off
i totally screwed mine up cause i left a custom bootscreen but my hacking computer is being repaired
Click to expand...
Click to collapse
lols thanks for reminding me to wipe my custom bootsplash lol just flashed leak3/ota but almost forgot to change my splash back to stock. =) and its outstandingly not stock haha
I didn't have to change it, just put the boot image on from 2.1 and I had it all perfect.
troubles
I've got to send mine back it is getting hot and it doesnt want to wake up when i hit the power button. I need to unroot. I will try what ive read here. But I am a novice any recommendations.
Update:
New Test build to see if it is finally working. I no longer have V500 to test with so if anyone wants to test and give me feedback.
Well it does not work...file removed
This will flash the persist.img from V510 to V500 which might be the key to get wifi and other hardware working. If it does not work and you need to flash old one back let me know. Make sure you back everything and be prepared to do a restore to stock if all else fails. That is the worst that can happen. Easy thing if it does not work is you flash the old persist.img which I will make if needed. I am downloading the TOT file now for v500 if it is needed...
Web Presence:
Twitter
Google+
Thanks to @Demetris for latest tip..
Thanks to @thoughtlesskyle and @Mixinitup4Christ for the system dump and all of their help.
Download HERE - File name V500_to_V510.zip
Awesome,good work!
Sent from my Nexus 7 using Tapatalk
Apart from Wifi and Bluetooth, is it functioning 100% Can it play games, which CM11 can't?
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Im assuming you did a factory reset first?
yes, i did
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
It should have not touched your recovery. Did you use the right button combo to the get into the factory reset screen and then keep pressing power button to get into TWRP?
Enter recovery mode do full wipe and try again
To enter recovery follow my guide in general
Through some miracle of button combinations i was able to get back into twrp. Back on CM. Thanks guys!
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
Happened to me too
Sent from my LG-G2 using Tapatalk
I have been trying to get wifi to work for the past few hours but no luck...
AndroidUser00110001 said:
I have been trying to get wifi to work for the past few hours but no luck...
Click to expand...
Click to collapse
Thank you for your awesome work!! I´m sure you´ll get it!:laugh:
somebody else having no sound from the speakers?
I mdofied patch and got 4.4.2 up and running but no wifi or bt yet
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
AndroidUser00110001 said:
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
Click to expand...
Click to collapse
not even download mode?
thoughtlesskyle said:
not even download mode?
Click to expand...
Click to collapse
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
AndroidUser00110001 said:
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
Click to expand...
Click to collapse
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
thoughtlesskyle said:
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
AndroidUser00110001 said:
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
Click to expand...
Click to collapse
i've never done something like that.........
Help! The phone dropped to the ground once and had a crack on the digitizer and LCD screen. I replaced both of them and now, it is stuck in a boot loop (turns on, stays on splash screen) I've tried flashing the latest firmware thru Odin, but the same thing happens. All I can do on the phone is just getting to the download mode. I can't get to recovery, too.
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Mukiai said:
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Click to expand...
Click to collapse
Yes, I did wipe both, I didn't do anything weird except a reboot, not rooted, stock ROM, pass on Odin, not similar to the hard brick problem. I can get to download and recovery mode.
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Mukiai said:
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Click to expand...
Click to collapse
I'm going to flash a new one.
Acerpeng229 said:
I'm going to flash a new one.
Click to expand...
Click to collapse
Any news? Do you enjoy again your Mega? Hope that yes.
No news ?
got same problem
Mukiai said:
No news ?
Click to expand...
Click to collapse
hello fellas..this my first post here..im using samsung mega lte,and have a problem after root my phones..cant go recovery mode.couse there have a red text warranty bit kernel and 3more text avove in my screen..just stuck at samsung logo..dont know how to do..there any friend here know how to do?its been a month my phone stuckat the same problem
It seems this issue is a difference in screen compatibility. To fix this, you can turn the device on and let it boot into the Android OS, then (while still on), unplug the old LCD and plug in the new LCD. Hit the power button to ensure the new LCD is working properly, then turn the device on, and finish assembling your phone.
same issue
R960 stuck in loop after replacing screen and cant access recovery or odin mode
need help desperately
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
-d.block- said:
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
Click to expand...
Click to collapse
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
trurl3 said:
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
Click to expand...
Click to collapse
I'm still a bit confused as to what exactly I should do.. there's alot in that thread.. I really can't afford to buy another screen. This really sucks that the update requires OEM screen in order to function.. if I could find a way to fix the issue without buying a screen I'd be extremely grateful!
But I don't have much experience at all with rooting and flashing custom ROMs, and I'm kind of afraid to brick the phone..
Any help to get the touch screen up and running would be highly appreciated!!
Thank you!
I am the only one who only a part of upper screen works? (I can see status bar, and rotating enter to wifi settings and try to get out of welcome screen of att)
Mukiai said:
No news ?
Click to expand...
Click to collapse
OMG! Sorry for the very late reply. It works fine already. Went to download mode and flashed using Odin. Thanks!
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.
Hi
I can remember exactly. But definetively since a while the fingerprint sensor is not working.
If it was after a update, I cant remember.
And in settings, I do not find any option for the sensor, e.g. adding a fingerprint.
It is EMUI 8 and phone bought in China for much less than 300€ some month ago in summer.
Probably bought a fake rip
Davilince said:
Probably bought a fake rip
Click to expand...
Click to collapse
No, this time no fake
It worked for somes quiet well. Since some weeks, nothing. Probably crappy SW Update, bad quality/test or so...
Small reset didnt helped.
Any other ideas, before try of big reset. Maybe this will help, maybe not. But lot of work to readjust settings...
Michael? said:
No, this time no fake
It worked for somes quiet well. Since some weeks, nothing. Probably crappy SW Update, bad quality/test or so...
Small reset didnt helped.
Any other ideas, before try of big reset. Maybe this will help, maybe not. But lot of work to readjust settings...
Click to expand...
Click to collapse
Try to wipe cache via recovery.
Santi_SAZ said:
Try to wipe cache via recovery.
Click to expand...
Click to collapse
Yeah, sounds like works. At Xiao Mi I was able, did it with several phones.
Ok, first full reset after backup. Still problem, then flash or waiting for next update...
Michael? said:
Yeah, sounds like works. At Xiao Mi I was able, did it with several phones.
Ok, first full reset after backup. Still problem, then flash or waiting for next update...
Click to expand...
Click to collapse
Try downloading last update through erecovery, or contact them
Santi_SAZ said:
Try downloading last update through erecovery, or contact them
Click to expand...
Click to collapse
already on latest EMUI. I even didnt unlock or changed anything. Thats why so disappointed. On Xiao Mi, root, unlock, ... and all worked fine. Here no change in system and xx stuff happens...
Michael? said:
already on latest EMUI. I even didnt unlock or changed anything. Thats why so disappointed. On Xiao Mi, root, unlock, ... and all worked fine. Here no change in system and xx stuff happens...
Click to expand...
Click to collapse
Yeah, is the easiest device to brick it. It bricks itself only watching it.
The eRecovery is a emergency recovery, I never used it, but you can try downloading last update package and flashing it, do a data backup before
Santi_SAZ said:
Yeah, is the easiest device to brick it. It bricks itself only watching it.
The eRecovery is a emergency recovery, I never used it, but you can try downloading last update package and flashing it, do a data backup before
Click to expand...
Click to collapse
no, i didnt brick it.
didnt do any unlock, or so. At Xiao Mi I did, and it worked without problems. Here I didnt do it, because to busy and OTA.
Did now,Factory reset, didnt bring any difference. Still no sensor on the bottom and fingerprint in settings.
Michael? said:
no, i didnt brick it.
didnt do any unlock, or so. At Xiao Mi I did, and it worked without problems. Here I didnt do it, because to busy and OTA.
Did now,Factory reset, didnt bring any difference. Still no sensor on the bottom and fingerprint in settings.
Click to expand...
Click to collapse
Since automatic EMUI check, I am on latest version. I think, if bad SW update I need to go back to older version. But this is difficult?
Any idea when next update is coming?
Michael? said:
Since automatic EMUI check, I am on latest version. I think, if bad SW update I need to go back to older version. But this is difficult?
Any idea when next update is coming?
Click to expand...
Click to collapse
I think, to version downgrade you need a unlocked bootloader, IDK whwn will be the next release, which is your model, C432, C636, C675?
Santi_SAZ said:
Yeah, is the easiest device to brick it. It bricks itself only watching it.
The eRecovery is a emergency recovery, I never used it, but you can try downloading last update package and flashing it, do a data backup before
Click to expand...
Click to collapse
So after hard reset, still ****ty SW or HW.
I dont understand, eRecovery.
I am already on latest EMUI. Even got update this week, but only security.... and security not so helpful currently, if phone not working so nice
Michael? said:
So after hard reset, still ****ty SW or HW.
I dont understand, eRecovery.
I am already on latest EMUI. Even got update this week, but only security.... and security not so helpful currently, if phone not working so nice
Click to expand...
Click to collapse
https://www.reddit.com/r/Huawei/comments/8yge1t/huawei_erecovery/
Santi_SAZ said:
https://www.reddit.com/r/Huawei/comments/8yge1t/huawei_erecovery/
Click to expand...
Click to collapse
BKL-AL00
reddet link i dont have that things there.
.reboot
.wipe da/factory reset (borh dones, stays with last SW version)
.wipe cache partition (no effect)
Hi guys, I broke my fingerprint when I replaced my lcd, meanwhile I received the update to EMUI 9. Ordered a new fingerprint, put it on place and nothing appears on the option. I thought that the fingerprint came damaged so I have ordered a new one. Put it in place and nothing again. Any ideas to get it work on EMUI 9 or we have to go back to the EMUI 8? Thanks guys
Madureira29 said:
Hi guys, I broke my fingerprint when I replaced my lcd, meanwhile I received the update to EMUI 9. Ordered a new fingerprint, put it on place and nothing appears on the option. I thought that the fingerprint came damaged so I have ordered a new one. Put it in place and nothing again. Any ideas to get it work on EMUI 9 or we have to go back to the EMUI 8? Thanks guys
Click to expand...
Click to collapse
Same happened with me but my sensor worked. Could've the supplier you're buying from
Santi_SAZ said:
I think, to version downgrade you need a unlocked bootloader, IDK whwn will be the next release, which is your model, C432, C636, C675?
Click to expand...
Click to collapse
Sorry, wasnt here for a while.
After big FW updrade, still no function. And still anoying chinese app, and too much Honor spam help/AI, whatever...
But I figured out, Cyanogen Mod available, yeah.
Am I right?
https://www.cyanogenmods.org/lineag...or_Lineage_OS_16_Android_90_Pie_Download_list
BKL-AL00 is what is written on the back of the case.
Shall I try it?
Maybe fingerprint returns, at least new FW.
Michael? said:
Sorry, wasnt here for a while.
After big FW updrade, still no function. And still anoying chinese app, and too much Honor spam help/AI, whatever...
But I figured out, Cyanogen Mod available, yeah.
Am I right?
https://www.cyanogenmods.org/lineag...or_Lineage_OS_16_Android_90_Pie_Download_list
BKL-AL00 is what is written on the back of the case.
Shall I try it?
Maybe fingerprint returns, at least new FW.
Click to expand...
Click to collapse
If you had a big FW and it didn't solve it, seems your fringerprint is broken
CyanogenMod is dead, now is LineageOS, you can try it, but if your sensor is fisically broken any ROM can bring it to life.
Santi_SAZ said:
If you had a big FW and it didn't solve it, seems your fringerprint is broken
CyanogenMod is dead, now is LineageOS, you can try it, but if your sensor is fisically broken any ROM can bring it to life.
Click to expand...
Click to collapse
yeah, agree. I forgot it.
but no fingerprint is not really annoying. in the next phone i could even renounce on it.
But interestingly (as u have maybe seens in the link) they are still bringing updates .... Even supporting Mi8 , as lineagoe.
So, better not to install it?
I would be even bit happier if I get rid of the original OS from honor...
Michael? said:
yeah, agree. I forgot it.
but no fingerprint is not really annoying. in the next phone i could even renounce on it.
But interestingly (as u have maybe seens in the link) they are still bringing updates .... Even supporting Mi8 , as lineagoe.
So, better not to install it?
I would be even bit happier if I get rid of the original OS from honor...
Click to expand...
Click to collapse
You can try it if you want, I think it wouldn't fix the fringerprint sensor.
First read the whole thread about LOS first before do anything https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-16-0-t3876509
Here is the link to download https://download.lineageos.org/berkeley