Related
Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App
HOW TO MAKE A PERFECT UNROOTED
ATTENTION
Before continuing, make... BACKUP, BACKUP, BACKUP, ...
If rooted ever your phone system detects it, and if you enter in Download this screen will look
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the box below you can read:
B73 and B100 = This is the State of the battery
Click to expand...
Click to collapse
And one of these three States:
ROOTED (Red) = The phone is rooted
UNROOTED (Pink) = The phone is not rooted, but once rooted. THIS STATE I'VE NEVER SEEN
UNROOTED (White) = The phone was never rooted.
Click to expand...
Click to collapse
According to the European legislation a terminal may be rooted without so we lose the warranty, but instead to use the phone we have to accept LG conditions that say that we can not customize the phone.
As it seems, commented by Spanish users that took your phone Technical Assistance Service (T.A.S.) still this rooted and with installed CWM, T.A.S. spent in warranty, so this method is not necessary, but you never know with whom you can bump sat, so here you have remove the ROOT and leave the phone as something out of factory.
UNROOTED METHOD
INFORMATION
This method serves to take the phone to the T.A.S., or if you want to leave it clean.
Download a ROM to your terminal, operated and country, use this link LG Phone Firmware G2
It enters to the CWM or TWRP Recovery.
Now get from:
CWM - Wipe Data / Factory Reset
TWRP - Advanced Wipeo, and the beams all but the SD.
Go to the reset menu or advanced and click on turn off.
While you press Volume+ connect the USB to the PC, enter Download Mode, as the images above
It runs Windows and follow this LG G2 Stock Firmware (Go Back to Stock)
Click to expand...
Click to collapse
CHECK IF IS or IS NOT ROOTED
In the dial pad type:
For the D800 3845#*800#
For the D801 3845#*801#
For the D802 3845#*802#
ETC
Go to the bottom of the menu and click on LG RCT then to Display Result
There are two possible results, Not rooted or Rooted
Click to expand...
Click to collapse
You are here too?! God Blessed G2 !
Gosh thanks so much!! I initially thought that the D802 doesn't have a root trip whoops.
Sent from my LG-D802 using xda app-developers app
TWRP - Advanced Wipeo, and the beams all but the SD.
Click to expand...
Click to collapse
Include internal storage, or not?
one problem with all that - "UNROOTED (White) = The phone was never rooted." should read "UNROOTED (White) = The phone isn't rooted at this time."
my d802 always returns to that state after I unroot and go back to stock I have to do 2 x full factory reset and using the power button down and vol down trick then if you go into download mode it always shows as unrooted in white.
Homero2 said:
HOW TO MAKE A PERFECT UNROOTED
ATTENTION
Before continuing, make... BACKUP, BACKUP, BACKUP, ...
If rooted ever your phone system detects it, and if you enter in Download this screen will look
In the box below you can read:
CHECK IF IS or IS NOT ROOTED
Click to expand...
Click to collapse
Hi, is it going reset root triper?? And, phone would still say rooted or unrooted! please advise.
twiztednibbz said:
one problem with all that - "UNROOTED (White) = The phone was never rooted." should read "UNROOTED (White) = The phone isn't rooted at this time."
my d802 always returns to that state after I unroot and go back to stock I have to do 2 x full factory reset and using the power button down and vol down trick then if you go into download mode it always shows as unrooted in white.
Click to expand...
Click to collapse
I don't understand what you mean
You say that there is an easier way of unrooted?
Homero2 said:
I don't understand what you mean
You say that there is an easier way of unrooted?
Click to expand...
Click to collapse
basically I cannot talk for any other model apart from d802 as this is what I have. but basically all you need to do to get it to show unrooted is to download the lg mobile support tool > open it > plug in usb while holding power and vol up with phone OFF to get into download mode > open the LG mobile support tool > go to options (top right) and press upgrade recovery.... the tool will download the original stock firmware onto the pc then install it on the phone. DO NOT unplug it until 100% on the PC. the phone will reboot about 80% on the pc but phone will have reached 100%. next do 2 factory resets using the power button and vol up method and you will find the unrooted status re-appears if you go back into download mode. Its also worth noting that it works best and flawlessly on com port 4 some ppl have experienced issues on other com ports.
obviously I accept no responsibility for you breaking your phone if you try it but I have done this at least 70 x to get out of bad fashes and it works every single one.
takes you about 30 min for the file to download but without that file downloading its probably about 5 minutes user input the longest/hardest bit being getting into the factory reset screen. lol.
twiztednibbz said:
basically I cannot talk for any other model apart from d802 as this is what I have. but basically all you need to do to get it to show unrooted is to download the lg mobile support tool > open it > plug in usb while holding power and vol up with phone OFF to get into download mode > open the LG mobile support tool > go to options (top right) and press upgrade recovery.... the tool will download the original stock firmware onto the pc then install it on the phone. DO NOT unplug it until 100% on the PC. the phone will reboot about 80% on the pc but phone will have reached 100%. next do 2 factory resets using the power button and vol up method and you will find the unrooted status re-appears if you go back into download mode. Its also worth noting that it works best and flawlessly on com port 4 some ppl have experienced issues on other com ports.
obviously I accept no responsibility for you breaking your phone if you try it but I have done this at least 70 x to get out of bad fashes and it works every single one.
takes you about 30 min for the file to download but without that file downloading its probably about 5 minutes user input the longest/hardest bit being getting into the factory reset screen. lol.
Click to expand...
Click to collapse
How do you choose which com port to use? Yes, I've experienced issues with com port 5
Sent from my LG-D802 using xda app-developers app
mab71 said:
How do you choose which com port to use? Yes, I've experienced issues with com port 5
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
ok so if press the start button on windows then type in device manager in the little box at bottom and press enter it will open up.
now put the phone in download mode (be sure to use a rear usb port too, then when the pc recognizes it go to your device manager, it will show Ports (COM & LPT) in the list and when you press the little plus sign to the left of the name you will see the phone and the port number being used. i.e. LGE AndroidNet USB Serial Port(COM7).
right click it and press properties > port settings tab > advanced > the COM port number is at the bottom of the box click it and select 4. it will probably tell you something else is using it but that is fine it makes no difference click ok then yes and ok again. Now your phone should show as COM Port 4 in the device manager. now close device manager and carry on using lg support tool.
twiztednibbz said:
basically I cannot talk for any other model apart from d802 as this is what I have. but basically all you need to do to get it to show unrooted is to download the lg mobile support tool > open it > plug in usb while holding power and vol up with phone OFF to get into download mode > open the LG mobile support tool > go to options (top right) and press upgrade recovery.... the tool will download the original stock firmware onto the pc then install it on the phone. DO NOT unplug it until 100% on the PC. the phone will reboot about 80% on the pc but phone will have reached 100%. next do 2 factory resets using the power button and vol up method and you will find the unrooted status re-appears if you go back into download mode. Its also worth noting that it works best and flawlessly on com port 4 some ppl have experienced issues on other com ports.
obviously I accept no responsibility for you breaking your phone if you try it but I have done this at least 70 x to get out of bad fashes and it works every single one.
takes you about 30 min for the file to download but without that file downloading its probably about 5 minutes user input the longest/hardest bit being getting into the factory reset screen. lol.
Click to expand...
Click to collapse
OK, I have personally tried port 5, and 45 port and not have had problems, since this method which I intend to use the official program, with the difference that we say you must firmware flasher.
Thank you for your information, I used the method proposed for some years with my KM900 and my P990, and I have to say that it works perfectly, and not only that, also the firmware that is installed is suitable to the country, model and telephone operator.
The two methods do the same thing, but his left it because I sometimes giving problems, there were times that said that the firmware that had was the more modern and wouldn't update, I am referring to below the D802 models
PD:
Factory Reset does so from 3845#*802#?
Homero2 said:
OK, I have personally tried port 5, and 45 port and not have had problems, since this method which I intend to use the official program, with the difference that we say you must firmware flasher.
Thank you for your information, I used the method proposed for some years with my KM900 and my P990, and I have to say that it works perfectly, and not only that, also the firmware that is installed is suitable to the country, model and telephone operator.
The two methods do the same thing, but his left it because I sometimes giving problems, there were times that said that the firmware that had was the more modern and wouldn't update, I am referring to below the D802 models
PD:
Factory Reset does so from 3845#*802#?
Click to expand...
Click to collapse
yeah I agree I have tried upto 9 different ports now and all seem to work for me but that is not the case for everyone. I know the whole process is supposed to be done on port 4 which is why I suggested it.
you are most welcome if I help but one person with my ramblings then that's a plus...
yes very true that it will put on the correct firmware for country model and telephone operator!
I have also encountered the same problems myself and this method I have never ever ever experienced one.
twiztednibbz said:
takes you about 30 min for the file to download but without that file downloading its probably about 5 minutes user input the longest/hardest bit being getting into the factory reset screen. lol.
Click to expand...
Click to collapse
Hello! Does your method work with a custom recovery and after the reset will it be gone?
i unrooted my D802 and when it was done my storage reduced from 32gb to 10gb . do you have any idea how to fix it?
What are differences between 10A-10B-20A-20B? I have a 16 GB Italy H3G D802, which rom have I to download?
I've checked a logs and found that com.lge.hiddenmenu.RCT_Check/RootingCheckActivity is running during that flow.
Then, dumped all framework and app files and searched for that activity.
Founded in HiddenMenu.odex file, deodexed ...
Actually they are reading value from that file: /persist/rct.cfg
There is second file that this activity cheks: /persist/rct
There is a logic there if file not exist /persist/rct then show RCT check disabled.
May be that will permanently disable root check?
There could be some other application (service or script) that actually doing root check and write this rct.cfg file.
---------- Post added at 03:59 PM ---------- Previous post was at 03:15 PM ----------
Tried to remove that two files.
But device restoring them after rebooting.
Needs to find a way how to log who is accessing that file.
Excuse me, I cannot understand.
I have to:
1 - Install CWM or TWRP
2 - Make a Full Wipe using CWM or TWRP
3 - Update firmware using normal procedure wich downloads and install the correct firmware on my phone
Is this correct?
I ask because doing only the 3rd point I still have "rooted" in download screen.
Perhaps I am missing the full wipe in TWRP.
Any help appreciated
OK, found description for rctd tool
Some workaround:
1. If you create two folders in target folder with the same names as that rct and rct.cfg names than rctd won't able to overwrite then, and from hidden menu device won't display rooted status;
2. Remove rctd tool and put clean files rct and rct.cfg from the unrooted device. Files could be found there.
But still OTA detect root
Redwid said:
OK, found description for rctd tool
Some workaround:
1. If you create two folders in target folder with the same names as that rct and rct.cfg names than rctd won't able to overwrite then, and from hidden menu device won't display rooted status;
2. Remove rctd tool and put clean files rct and rct.cfg from the unrooted device. Files could be found there.
But still OTA detect root
Click to expand...
Click to collapse
Ok, looks like from 4.4.2 rtcd no longer exists but you need the files in /persist folder.
So this should not be a problem.
You root only adb, you take the files and put them in a safe place.
You do whatever you want.
You restore the 2 files (while you're root)
You do a full wipe and a firmware recovery.
Thos should take it to a total unroot phone.
Am I right?
lmerega said:
Ok, looks like from 4.4.2 rtcd no longer exists but you need the files in /persist folder.
So this should not be a problem.
You root only adb, you take the files and put them in a safe place.
You do whatever you want.
You restore the 2 files (while you're root)
You do a full wipe and a firmware recovery.
Thos should take it to a total unroot phone.
Am I right?
Click to expand...
Click to collapse
Sorry, don't know. I'm trying to find a way install OTA update on rooted device.
Don't like to do a full wipe.
---------- Post added at 10:28 AM ---------- Previous post was at 09:34 AM ----------
BTW to find out if you have root checker do this command in the shell:
Code:
ps | grep rctd
Edited to add data I found in recovery mode:
"HTC/htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam10121728"
And there are a bunch of error messages ending in:
"E: failed to mount /cache (Invalid argument).. try emmc mount)
E: Can't find device node for mount point /cache"
Can anybody point me to a good resource explaining how I can attempt to apply an image from the sd card?
Or how to check if usb debugging is switched on?
Original post:
When I unplugged my HTC M9 this morning it was on a screen saying the phone is encrypted and prompts to enter the screen lock password. I enter what I think is the correct code (I've been using pattern unlock but put in the code i used to use) and it tells me its correct but the data is corrupted and it needs to do a factory reset.
There is no other option apart from accepting the factory reset.
When I accept the factory reset it just says 'rebooting...' and then never does (I waited an hour).
I've tried the obvious holding down volume up and power off.
I can get to the options screen to choose reboot, download mode, recovery etc. I tried reboot (obviously) but it only boots back to the decrypt screen. I also tried recovery mode and I got a picture of a phone with a red warning triangle containing an exclamation mark and nothing else happened. I tried pressing power and volume up and it just rebooted back to the decrypt screen.
It says it is:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
It's a carrier-free version, bought from Amazon UK. I haven't done anything to it (I used to root and flash custom roms but not for 2-3 years - I have a nearly 2-year old - so my knowledge is mostly forgotten and out of date).
I have no reason to think that usb debugging is on so I'm worried that there is nothing I can do.
Edit: Maybe I can install something from the sd card. I'm going to try that.
Any suggestions greatly appreciated.
srjones said:
Edited to add data I found in recovery mode:
"HTC/htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam10121728"
And there are a bunch of error messages ending in:
"E: failed to mount /cache (Invalid argument).. try emmc mount)
E: Can't find device node for mount point /cache"
Can anybody point me to a good resource explaining how I can attempt to apply an image from the sd card?
Or how to check if usb debugging is switched on?
Original post:
When I unplugged my HTC M8 this morning it was on a screen saying the phone is encrypted and prompts to enter the screen lock password. I enter what I think is the correct code (I've been using pattern unlock but put in the code i used to use) and it tells me its correct but the data is corrupted and it needs to do a factory reset.
There is no other option apart from accepting the factory reset.
When I accept the factory reset it just says 'rebooting...' and then never does (I waited an hour).
I've tried the obvious holding down volume up and power off.
I can get to the options screen to choose reboot, download mode, recovery etc. I tried reboot (obviously) but it only boots back to the decrypt screen. I also tried recovery mode and I got a picture of a phone with a red warning triangle containing an exclamation mark and nothing else happened. I tried pressing power and volume up and it just rebooted back to the decrypt screen.
It says it is:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
It's a carrier-free version, bought from Amazon UK. I haven't done anything to it (I used to root and flash custom roms but not for 2-3 years - I have a nearly 2-year old - so my knowledge is mostly forgotten and out of date).
I have no reason to think that usb debugging is on so I'm worried that there is nothing I can do.
Edit: Maybe I can install something from the sd card. I'm going to try that.
Any suggestions greatly appreciated.
Click to expand...
Click to collapse
This is the M9 forum, so the advice we have here is for that device. Head over to the M8 forum for help specifically tailored to your phone.
Typo!
computerslayer said:
This is the M9 forum, so the advice we have here is for that device. Head over to the M8 forum for help specifically tailored to your phone.
Click to expand...
Click to collapse
Thanks, sorry, it is an M9. I initially thought it was an M8 and had to google the difference so I must have been thinking of that. Have edited the post now
srjones said:
Thanks, sorry, it is an M9. I initially thought it was an M8 and had to google the difference so I must have been thinking of that. Have edited the post now
Click to expand...
Click to collapse
In that case, check out the readme thread at the top of this forum. It has all you'll need to find the correct RUU and apply it properly.
computerslayer said:
In that case, check out the readme thread at the top of this forum. It has all you'll need to find the correct RUU and apply it properly.
Click to expand...
Click to collapse
Thanks for your reply, but are you sure? As I said in my post, the device is locked, S-ON and usb debugging is not switched on and I cant get into the phone to turn it on. The normal instructions seem to assume that I can turn usb debugging on.
Thanks again for your time
srjones said:
Thanks for your reply, but are you sure? As I said in my post, the device is locked, S-ON and usb debugging is not switched on and I cant get into the phone to turn it on. The normal instructions seem to assume that I can turn usb debugging on.
Thanks again for your time
Click to expand...
Click to collapse
I am sure ...and the readme thread explains this too. Take some time to read through it, especially the post about RUUs.
You mention not getting the phone to turn on....do you mean that it won't power on at all or that it won't boot? If it does turn on, what do you see?
[EDIT] Re-reading your original post, you say that you can get into download mode. If this is still the case, then you should be able to apply the appropriate RUU. Again, the readme thread has all you need to get that going[/EDIT]
Thank you, you've been incredibly patient. I'd got a bit discouraged at the scale of the problem. It makes it much easier to know that a fix should be possible at the end of the process.
srjones said:
Thank you, you've been incredibly patient. I'd got a bit discouraged at the scale of the problem. It makes it much easier to know that a fix should be possible at the end of the process.
Click to expand...
Click to collapse
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
computerslayer said:
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
Click to expand...
Click to collapse
Hi, I've been reading post #3 in the reader (all seems very straightforward, I feel foolish for not persisting in the first place). I still need to get a card reader to get a ruu onto the card from my pc but im trying to get the right ruu ready now.
In download mode I have a line that says OS-3.35.401.32
I think this means that I look in the SKU 401 section but then there isn't a file for my exact number, the closest ends in .12 rather than .32
Does this mean that I need to look in other places to get one that matches exactly?
Thanks again
srjones said:
Hi, I've been reading post #3 in the reader (all seems very straightforward, I feel foolish for not persisting in the first place). I still need to get a card reader to get a ruu onto the card from my pc but im trying to get the right ruu ready now.
In download mode I have a line that says OS-3.35.401.32
I think this means that I look in the SKU 401 section but then there isn't a file for my exact number, the closest ends in .12 rather than .32
Does this mean that I need to look in other places to get one that matches exactly?
Thanks again
Click to expand...
Click to collapse
Sounds like you've read it well! Don't be too hard on yourself - there is a lot to take in. From your OS version your SKU is indeed 401.
You're good to use the RUU 3.35.401.12 even though your current version ends in .32 (from the readme: "In other words the part marked with y of x.xx.xxx.yy is allowed to differ whereas x needs to be the same for your current firmware version and the RUU").
computerslayer said:
Sounds like you've read it well! Don't be too hard on yourself - there is a lot to take in. From your OS version your SKU is indeed 401.
You're good to use the RUU 3.35.401.12 even though your current version ends in .32 (from the readme: "In other words the part marked with y of x.xx.xxx.yy is allowed to differ whereas x needs to be the same for your current firmware version and the RUU").
Click to expand...
Click to collapse
Aah, thanks. Amazing what I can miss even after I think I've read it "thoroughly".
computerslayer said:
The first time going through this kind of thing is always a bit intimidating. After going through it a few times it becomes familiar.
Read through the RUU section in the readme thread. As it'll describe, you'll need your OS version to determine your SKU which will lead you to the right RUU and so on. Post here if you've got questions along the way.
Click to expand...
Click to collapse
Hi, I'm following the Instructions for the SD card method from post #3 of the readme. I've just done step 5: "You will be asked whether you want to flash the file. Confirm with the volume up button"
The phone is now vibrating regularly every (approx) 3 seconds and flashing a silver HTC logo on the screen. I'm pretty sure this isn't normal. This isn't normal, right?
It's been doing it for several minutes.
Do you have any suggestions? Maybe leave it for a good long while and then try holding down power and volume up?
srjones said:
Hi, I'm following the Instructions for the SD card method from post #3 of the readme. I've just done step 5: "You will be asked whether you want to flash the file. Confirm with the volume up button"
The phone is now vibrating regularly every (approx) 3 seconds and flashing a silver HTC logo on the screen. I'm pretty sure this isn't normal. This isn't normal, right?
It's been doing it for several minutes.
Do you have any suggestions? Maybe leave it for a good long while and then try holding down power and volume up?
Click to expand...
Click to collapse
It doesn't seem normal, I must admit. I think I'd let it go for about 30 minutes to see if it is rebooting as part of the RUU installation. After that, I'd force it to power off and re-try the attempt - though I might re-download the RUU matching my SKU and use that instead. It could be that your download got corrupted.
There is a way to check the MD5 sum of your download to confirm the integrity of your file. I haven't done that in a while, but I recall that there are plenty of tools easily available (Google will help you here).
computerslayer said:
It doesn't seem normal, I must admit. I think I'd let it go for about 30 minutes to see if it is rebooting as part of the RUU installation. After that, I'd force it to power off and re-try the attempt - though I might re-download the RUU matching my SKU and use that instead. It could be that your download got corrupted.
There is a way to check the MD5 sum of your download to confirm the integrity of your file. I haven't done that in a while, but I recall that there are plenty of tools easily available (Google will help you here).
Click to expand...
Click to collapse
Thanks, the MD5 sum is fine (managed to take in that bit of the read me).
I tried to use the ruu again just to be sure but there's no difference.
I think it's not able to apply the ruu at all. It takes no time at all before it does the buzzing/ flashing thing and when i force a restart I still have the exact same error message in recovery mode. Like maybe it started by trying to wipe the cache, couldn't find it, tried to format and mount again, but couldn't find the device node (not totally sure there) and then gave up.
I used to use Linux a long time ago (was never an expert) and if I saw this sort of thing with a pc, I'd be repartitioning the hard drive while googling the price of a new one. I just don't know enough about Android (i know nothing about Android) to work it out though.
I took a photo of the error message using another phone, is it worth trying to post it? I don't know how to do that and will have to spend time finding out which is why I'm asking rather than just posting out.
srjones said:
Thanks, the MD5 sum is fine (managed to take in that bit of the read me).
I tried to use the ruu again just to be sure but there's no difference.
I think it's not able to apply the ruu at all. It takes no time at all before it does the buzzing/ flashing thing and when i force a restart I still have the exact same error message in recovery mode. Like maybe it started by trying to wipe the cache, couldn't find it, tried to format and mount again, but couldn't find the device node (not totally sure there) and then gave up.
I used to use Linux a long time ago (was never an expert) and if I saw this sort of thing with a pc, I'd be repartitioning the hard drive while googling the price of a new one. I just don't know enough about Android (i know nothing about Android) to work it out though.
I took a photo of the error message using another phone, is it worth trying to post it? I don't know how to do that and will have to spend time finding out which is why I'm asking rather than just posting out.
Click to expand...
Click to collapse
It's certainly better than nothing - and I'm interested to hear more about an error message. I haven't applied a RUU in a while, but I don't recall the phone ever booting into recovery.
Try formatting data in TWRP recovery. It will wipe your internal memory though. This fixes the issue on the 10.
computerslayer said:
It's certainly better than nothing - and I'm interested to hear more about an error message. I haven't applied a RUU in a while, but I don't recall the phone ever booting into recovery.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, it doesn't boot into recovery mode straight away, it just dies a bootloop. I then hold down various buttons to get to the boot loader. Hopefully I've added the picture correctly.
Edit: I can't see the photo. I don't know why it's not working. It is here https://imgur.com/gallery/vkP5Z
Did I do something stupid? Is imgur not the right thing to use?
side_flip15 said:
Try formatting data in TWRP recovery. It will wipe your internal memory though. This fixes the issue on the 10.
Click to expand...
Click to collapse
Thanks, I'm not sure what 'Formatting data in TWRP recovery' means. Posts #4 and #5 of the readme mention TWRP. Do i need to download one of the linked backups and use it to restore?
srjones said:
Thanks, I'm not sure what 'Formatting data in TWRP recovery' means. Posts #4 and #5 of the readme mention TWRP. Do i need to download one of the linked backups and use it to restore?
Click to expand...
Click to collapse
Let's back up a step - do you have TWRP installed? Unless you received the phone from someone who installed it themselves, you'd have to have done this yourself (by unlocking the bootloader & flashing TWRP via ADB) - so if you don't know, you probably don't.
If you did receive the phone from someone else and want to check:
boot into download mode (PWR-VOLDWN)
use the volume keys to highlight 'boot into bootloader' and the power key to select that option once it is highlighted
use the volume keys to highlight 'boot into recovery' & the power key to select that option once it's highlighted
If you have TWRP installed, you'll see the blue TWRP logo and name. Otherwise you'll be loaded into the stock Android recovery. You can back out by using the volume keys to navigate and the power button to select the option to get out.
computerslayer said:
Let's back up a step - do you have TWRP installed? Unless you received the phone from someone who installed it themselves, you'd have to have done this yourself (by unlocking the bootloader & flashing TWRP via ADB) - so if you don't know, you probably don't.
If you did receive the phone from someone else and want to check:
boot into download mode (PWR-VOLDWN)
use the volume keys to highlight 'boot into bootloader' and the power key to select that option once it is highlighted
use the volume keys to highlight 'boot into recovery' & the power key to select that option once it's highlighted
If you have TWRP installed, you'll see the blue TWRP logo and name. Otherwise you'll be loaded into the stock Android recovery. You can back out by using the volume keys to navigate and the power button to select the option to get out.
Click to expand...
Click to collapse
Ah, right, no, nothing non-standard installed. So that's not an option. Thanks
In this guide, I will show how to how to change from LVM to Chinese unification storage method. Windows OS Only.
This guide is specifically for Oppo Find 7(A/S).
The idea of changing to chinese unification storage method is to have access to 8.1 Android operating system and future Android OS builds.
Please follow these following steps in order be able to run 8.1 Android on your OPPO Find 7.
1) Back up only your internal storage because after you flash the following tools, the internal storage will be wiped completely.
2) Download this file (for OPPO Find 7s) and this file (for OPPO Find 7a) then run the following steps:
Extract the files, and locate the QcomMtk_Driver_Setup.exe (*install this driver*) and reboot your computer system.
After rebooting, take off the battery off the Oppo find 7 and press the volume up button and connect to the PC using a micro USB cable. Go to the device manager, open the ports tab and there should be something like qualcomm etc. If there is no warning sign then you are fine and you should proceed along the steps. If there is a warning sign, just right click on the driver and update by letting windows finding the appropriate drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then go back to the folder where you extract the zip file and locate (X9077_Android5.0_32G_20150520.exe) or X9007 respectively and run as administrator. rights only.
Agree with the licence. As shown in the image.
Now, again, make sure your battery is removed, hold volume up button and connect to the pc.
Click the first top left button as indicated in the image below.
Now, the software should do the rest so please be patient and wait until the green line has finished and the timeclock down on the bottom right as come to a halt.
After the green line has finished, please remove your device and plug back your battery. Let the device fully boot up before moving on the following steps.
After you get to the setup screen. Press and hold the power off button and shutdown fully before going back to the fast boot mode by pressing volume up and power button at the same time, the battery needs to be installed this time.
-
Now, flash the twrp modded image using fast boot flash and download the two files fastboot and twrp-modded img :
1) Have your phone in bootloader mode. (Turn off your phone, press volume up button and power button together and connect usb).
2) Navigate to the folder and click on the top left of the folder and copy that. e.g C:\Users\samgi\Desktop\platform-tools
3) Open cmd and type in: cd C:\Users\samgi\Desktop\platform-tools
4) In cmd type in: fastboot flash recovery image-modded.img
4) Remove USB and press power button and volume down button simultaneously.
-After you have flashed the recovery, boot into recovery and store the ROM, GAPPS and cm13 unified patch in the external sd card using your USB.
Download your favourite 9.0 ROM:
crDroid for example: https://androidfilehost.com/?w=files&flid=262369
Install GAPPS (only pico):
http://opengapps.org/
After you have downloaded all the files rom gapps cm13 patch etc. Make sure to flash each of the zip files one by one:
1) Flash ROM
2)Flash Pico Gapps
3)Flash CM13 Patch here
So basically, just head over to https://download.lineageos.org/find7 and download the latest Lineage OS 16 ROM. Then download the MindTheGapps (since pico OpenGapps can't work) from https://androidfilehost.com/?w=files&flid=170282 make sure to get 9.0.0arm.
Reboot to recovery, wipe the dalvik, system and cache. Then proceed with installing the the LOS 16 ROM. After that, you can flash the CM 13 patch and the gapps (MindTheGapps). It's ok to do gapps first before the CM 13 patch. I noticed that it makes no difference. Works the same every time.
Well, that's about it, reboot and enjoy. OTA should work after this. I think.
Good luck.
Then, simply clear cache and boot to your 9.0 OS. P.S don't forget to restore your data that you deleted in step one.
Optional: If you want to go back to Color OS or you have hard-bricked your OPPO Find 7(A/S) this tool will help you get back to stock firmware.
STOCK FIRMWARE (LVM)
Here are the instructions to unbrick your phone:
This is going to be a step by step guide on how to unbrick your OPPO FIND 7 (A/S)
Before attempting this guide, Windows is needed to be in "Test Mode".
To do this:
1) Open CMD with admin rights, and type "bcdedit /set testsigning on" without the colons.
2) Restart your computer.
End result:
This will check if this guide is applicable.
Note: Make sure your device has at least 70% battery. Charge it for an hour or so if you are not sure about the amount of battery left.
Note 2: I'll assume you are an admin of the computer you are using.
1) Disconnect your device from your charger/computer, etc.
2) Take out the battery and wait for 5 seconds.
3) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
4) Release your hands, and go to Device Manager. (How to go to device manager below)
1. Click the start menu
2. Right click Computer (Right hand side)
3. Click Properties
4. On the left hand side, click on Device Manager
5) Under Ports, you'll see either QHSUSB_BULK or Qualcomm *blah blah blah* 9006/9008
If you don't see any of the three, you're doing it wrong (Probably).
If you're not seeing it, try connecting your device without the battery.
Next, we uninstall the drivers. Simple enough.
WARNING: This part is only for people seeing Qualcomm 9006/9008 in Device Manager.
1) Uninstall the driver. (Right click your device, then click Uninstall. If prompted, delete driver software too)
2) Unplug your device.
3) Take out the battery and wait for 5 seconds.
4) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
5) Release your hands, and go to Device Manager.
You should see QHSUSB_BULK, if not, you might be doing it wrong.
Now we install the proper drivers.
NOTE: You should be seeing QHSUSB_BULK in your Device Manager, if not you're doing it wrong.
1) Download the Find 5 Drivers and unzip the file anywhere.
2) Right click on your device showing QHSUSB_BULK and click on Update Driver Software.
3) Click on "Browse my computer for driver software", and select the folder in which you extracted the drivers to.
4) It will install automagically. If prompted, click on Install the driver anyway.
After installing, your device should say Qualcomm *blah blah blah* 9006/9008.
The moment all of you have been waiting for. Unbrick!
NOTE: Your device should be connected at all times.
1) Download the tool that will save you below.
2) Extract the contents from the zip file.
3) Open the .exe file with admin rights.
4) There should be a line that is visibly different from others.
5) If there is, click start and wait till that line turns green. (It takes a few minutes. Generally nothing should go wrong at this stage.) If there isn't, you're doing it wrong.
6) After the line turns green, unplug your device and hold the power button until you see the Oppo logo.
7) If all goes well, you should be booted to ColourOS v1.2.5i.
If everything went through smoothly, you should be unbricked and ready to brick your device again.
Special thanks to:
@tashimotor https://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
@Manas1796 thread: https://forum.xda-developers.com/find-7/general/7-dead-development-oppo-7-terminated-t3764649
@crdroid
@ akmlfhm https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802
@play8oy
A very helpful thread, my friend! Thanks for keeping us up to date that this is possible!
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Sure, I will let you know once I upload the file to Google Drive. :fingers-crossed:
Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....
itmdn said:
Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....
Click to expand...
Click to collapse
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
1. This guide is for Oppo Find 7s. The 8.1 android OS does not recognise X9076 (LVM) and shows "encryption unsuccessful" whenever you boot into the OS. However, when your phone shows X9077 (Chinese unified method) the 8.1 recognises and lets you boot successfully. I'm not quite sure why OPPO had to make this sooooo confusing. Lol.
2. I am running the latest Windows 10 Anniversary Update.
3. I'm not sure what you're asking ? It does not matter 32-bit or 64 bit
4. I'm literally running CrDroid and its amazing, the latest update just got out online check it out.
Let me know if you need further help.
brownboy1289 said:
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
sorry, is this your mean u will upload the X9076_Android5.0_32G_20150520 version?
or you are saying that files at OP is working for X9076 and X9077 ?
sorry .... cant wait anymore ... really need switch from lvm to chns unified and taste the Android 8.1
tq
Click to expand...
Click to collapse
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
Click to expand...
Click to collapse
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide
itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide
Click to expand...
Click to collapse
I'm glad that it is working for you. :fingers-crossed::good:
Let me know if you have any problems
Sorry for those waiting on the OPPO FIND 7a files, I have really slow upload speed.
5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Up and running: https://drive.google.com/file/d/1h74LKVucM4RoBJ-Bsgkmzdavzn_MbtPY/view?usp=sharing
Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq
itmdn said:
Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq
Click to expand...
Click to collapse
What's the problem? I think they had a 7.1 forum but I'm not sure if it's closed
If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.
itmdn said:
If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.
Click to expand...
Click to collapse
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.
brownboy1289 said:
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.
Click to expand...
Click to collapse
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq
That,s weird battery usage. When I leave a 100% battery at night, next morning ( about 8 hours) I have about 90+% left, and I leave WiFi and mobile data on all night. Though I use Servicely and Project Skynet Raising.
itmdn said:
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq
Click to expand...
Click to collapse
This is a strange problem I'm not quite sure how to help... sorry
Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq
itmdn said:
Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq
Click to expand...
Click to collapse
Best advice would be to reflash the ROM with pico gapps or at last change to another 8.1 ROM i.e lineage rom or omni 8.0
I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.
You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.
My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.
To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz
Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?
paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !
Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?