Hello
Seems like my LeMax2 is hardbricked.
Current Situation
Mobile starts with double vibrate, loads splash screen, waits for like 10 second and restarts again.
I can only enter into fastboot mode and QIFL Download mode.
What I have tried already with no success
QIFL Fastone restore
Full format with all partition tables
Installed almost all roms available via fastboot
Installed almost all recoveries but if entering into recovery it only shows splash of recovery with Leeco logo and restarts again.
Discharged mobile for a day
Kept it charging for a day
One of expert from XDA also helped with Teamweaver for almost 4 hours but no success.
I have been told the last thing I can try is if someone can give me a full diskdump of their own working LeMax2 829 preferably stock then it may work, this is the last thing I want to spend my time on before throwing it away and buying a new phone, my own guess is that partition table is corrupted or rom have bad sector so if anyone can help please I will be extremely thankful.
you have tried to unbrick with qfil service rom like it is described here:
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
???
I had the same situation and it worked for me!
He tried everything, really! This is stuff for an expert or anyone who run into the same Problem and was able to fix it. Maybe writing a full dd image (meanig really everything, not only some files|partitions) will do it. imei and mac adresses will be blanked of course. This is not about pulling files or partitions, its dumping the whole flash content to one file!
So: DD image needed badly, best same model, untinkered.
Another question:
Can somebody tell how to recreate the partition table properly? i mean not erasing content or formatting - recreating|repartitioning.
I know how it works on Samsung but it's totally different.
My thoughts are:
-Messed up partition table
-flash either physically defective or somehow Locked for read-only
-other Hardware/Software fault
I already threw one x829 away which had almost the same Problem.
I bet there will be more threads about malfunctioning x829 soon...
Gesendet von meinem Le X820 mit Tapatalk
---------- Post added at 02:41 PM ---------- Previous post was at 02:29 PM ----------
@craftvision, i have 1 (strange) idea. Today i received my spare x2 and while tinkering with the device, i made something stoopid wich could be of use...
Fixed it in 1 minute again but was surprised it worked...
Of course, chances are low...
Gesendet von meinem Le X820 mit Tapatalk
Yes we have tried everything and every possible way with QIFL too,
A.N.Droid said:
A.N.Droid
Click to expand...
Click to collapse
has spent his more than 8 hours of his personal time with me on Teamweaver, he is really a good helpful guy and a real Android expert, big thanks to him for all his time.
Phone is still in same condition, only loads splash for 10 seconds and restarts and enters only in QFIL Download or Fastboot mood, all installations are still successful, seeings new Splash screens with every rom that I could install via fast but but boot loop and no recovery.
craftsvision said:
Yes we have tried everything and every possible way with QIFL too, has spent his more than 8 hours of his personal time with me on Teamweaver, he is really a good helpful guy and a real Android expert, big thanks to him for all his time.
Phone is still in same condition, only loads splash for 10 seconds and restarts and enters only in QFIL Download or Fastboot mood, all installations are still successful, seeings new Splash screens with every rom that I could install via fast but but boot loop and no recovery.
Click to expand...
Click to collapse
Happened to me with a Oneplus One. Rarely it booted but it had random reboots on every rom from minute to minute. My guess is that something is fuc*ed up inside the phone. Never found a solution, just bought a new motherboard. My guess was that the EMMC or something broke
craftsvision said:
Hello
Seems like my LeMax2 is hardbricked.
Current Situation
Mobile starts with double vibrate, loads splash screen, waits for like 10 second and restarts again.
I can only enter into fastboot mode and QIFL Download mode.
What I have tried already with no success
QIFL Fastone restore
Full format with all partition tables
Installed almost all roms available via fastboot
Installed almost all recoveries but if entering into recovery it only shows splash of recovery with Leeco logo and restarts again.
Discharged mobile for a day
Kept it charging for a day
One of expert from XDA also helped with Teamweaver for almost 4 hours but no success.
I have been told the last thing I can try is if someone can give me a full diskdump of their own working LeMax2 829 preferably stock then it may work, this is the last thing I want to spend my time on before throwing it away and buying a new phone, my own guess is that partition table is corrupted or rom have bad sector so if anyone can help please I will be extremely thankful.
Click to expand...
Click to collapse
Instead of throwing it away, please send it to me, pay your shipping ......
I was going to say the same thing here do not throw it away, I own a x829 for about one week and love this thing.
Yes, try replacing the whole memory block. That would be the best way to rule out hardware fault.
Tushar1 said:
Yes, try replacing the whole memory block. That would be the best way to rule out hardware fault.
Click to expand...
Click to collapse
I think we cannot even buy only memory block, I guess I have to buy complete mother board, and so far I could not even find a complete motherboard set online anywhere.
theese bga's are not easy to exhange. best would be an infrared reworkstation with ir preheater. if you aren't familiar with bga reballing, i think the chance you get it right is under 1%.
i have a cheap hot-air solder station, self made preheater, ir-thermometer, thermo-couple and lot of required tools. the equipment is sufficient to do simple reflows on xbox, playstation, whatever electronics... however, this is not a professional fix and not sufficient to do bga reballings. you need to follow a temperature curve, it's tricky (for me at least). you can try to put it in the oven with no-clean flux but chances are high you will ruin it. plastic melts easily, capacitors tend to "popcorn" when too much/too long heat is apllied.
Gesendet von meinem Le X820 mit Tapatalk
Is there a way to convert a Recovery rom to a fastboot rom?
I tried this method
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
That converted system.new.dat to system.img but while flash it gives this error "Invalid sparse file format at header magi" and then fastboot command crashes..!
I want to convert CN26 flash able via fastboot because it was most successful rom for me so far!
craftsvision said:
Is there a way to convert a Recovery rom to a fastboot rom?
I tried this method
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
That converted system.new.dat to system.img but while flash it gives this error "Invalid sparse file format at header magi" and then fastboot command crashes..!
I want to convert CN26 flash able via fastboot because it was most successful rom for me so far!
Click to expand...
Click to collapse
craftsvision said:
I think we cannot even buy only memory block, I guess I have to buy complete mother board, and so far I could not even find a complete motherboard set online anywhere.
Click to expand...
Click to collapse
No I didn't mean that you should buy emmc(the flash storage) or the motherboard. I meant the whole partition dump of a working device. I won't be able to find a le max 2, but I can help you with the flashing. The header sparse thing means it needs to be in sparse chunks or even the sparse header at the top of the image file. The file is bigger than what your device supports, so it will send it out in chunks. Sometimes it automatically starts after waiting for a few minutes. It would be much easier to just flash it by TWRP. Have you tried flashing recovery partition or directly booting to twrp from the fastboot bootloader screen?
Tushar1 said:
No I didn't mean that you should buy emmc(the flash storage) or the motherboard. I meant the whole partition dump of a working device. I won't be able to find a le max 2, but I can help you with the flashing. The header sparse thing means it needs to be in sparse chunks or even the sparse header at the top of the image file. The file is bigger than what your device supports, so it will send it out in chunks. Sometimes it automatically starts after waiting for a few minutes. It would be much easier to just flash it by TWRP. Have you tried flashing recovery partition or directly booting to twrp from the fastboot bootloader screen?
Click to expand...
Click to collapse
Yes, have tried flashing all recoveries available in recovery partition or even in boot partition. A.N.Driod has also flashed his own x829 diskdump on my phone but no success.
Only fastboot and QIFL Download is available at this phone...
craftsvision said:
Yes, have tried flashing all recoveries available in recovery partition or even in boot partition. A.N.Driod has also flashed his own x829 diskdump on my phone but no success.
Only fastboot and QIFL Download is available at this phone...
Click to expand...
Click to collapse
Are you able to boot into some image through fastboot? Like, "fastboot boot recovery.img"
Tushar1 said:
Are you able to boot into some image through fastboot? Like, "fastboot boot recovery.img"
Click to expand...
Click to collapse
no, flash is success but loads only splash of recovery, waits for 10 seconds and reboots again. Have tried all versions of TWRP available
Don't flash recovery, you can directly boot from the fastboot screen. Instead of "fastboot flash recovery twrprecovery.img" do "fastboot boot twrprecovery.img".
Tushar1 said:
Don't flash recovery, you can directly boot from the fastboot screen. Instead of "fastboot flash recovery twrprecovery.img" do "fastboot boot twrprecovery.img".
Click to expand...
Click to collapse
That too negative, it loads normal splash and then restarts
And you have tried flashing stock sparse images with qfil?
Tushar1 said:
And you have tried flashing stock sparse images with qfil?
Click to expand...
Click to collapse
if you are talking about exactly this method then yes done 100 times already
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
craftsvision said:
if you are talking about exactly this method then yes done 100 times already
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
Click to expand...
Click to collapse
There is probably a hardware problem with the device. The internal storage should be ok as the qfil flashing should fail and the device would not boot in any way if that was the case.
If you have successfully flashed through qfil, there is no reason for a boot problem...
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
Btw, the above link you provided is for x820 which is 32 gb version, i think. X829 is 64 gb, maybe try this? https://forum.xda-developers.com/le-max-2/how-to/official-fastboot-rom-x829-regular-twrp-t3620591
Related
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE:full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
hi,
i wanted to flash stock android (used an rom before) so i erase recovery system etc.. and when i want to flash the system img it says "
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
-.- what can i do ?
any solutions ?
thanks
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
enriquejones666 said:
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
Click to expand...
Click to collapse
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
disturbd1 said:
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
Click to expand...
Click to collapse
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
tdct12 said:
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
Click to expand...
Click to collapse
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
disturbd1 said:
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
Click to expand...
Click to collapse
Just download the newest build and fastboot flash bootloader bootloader.img :good:
oediv said:
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
Click to expand...
Click to collapse
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
enriquejones666 said:
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
Click to expand...
Click to collapse
2 people 1 idea
It's on the way, I said " want to update the OS and Made a factory reset before"
Have you tried flashing the factory images with fastboot? Pretty straight forward...
For future reference, how did you erase things with the bootloader locked?
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC
Has anyone done a ROM backup (preferably scatter, but a fastboot backup may do) for these things? Been trying to get this demo unit to cooperate with SP Flash Tool lately, but I end up with a DA DOWNLOAD FAIL error. @diplomatic says this may be due to a restricted bootloader or something along the lines of it (MTK bootloaders by design are able to restrict access to SPFT afaik), but does anyone have or know how to get this off a working device?
blakegriplingph said:
Has anyone done a ROM backup (preferably scatter, but a fastboot backup may do) for these things? Been trying to get this demo unit to cooperate with SP Flash Tool lately, but I end up with a DA DOWNLOAD FAIL error. @diplomatic says this may be due to a restricted bootloader or something along the lines of it (MTK bootloaders by design are able to restrict access to SPFT afaik), but does anyone have or know how to get this off a working device?
Click to expand...
Click to collapse
Have you already tried holding volume up and/or volume down while inserting the cable? Or even disconnecting the battery? This might force it into boot ROM mode (Mediatek USB Port).
diplomatic said:
Have you already tried holding volume up and/or volume down while inserting the cable? Or even disconnecting the battery? This might force it into boot ROM mode (Mediatek USB Port).
Click to expand...
Click to collapse
Hmm, let me try that. I can more or less rule out the battery method as I have to crack this thing open i.e. heat up the touchscreen to gain access to the battery. :/
Bumping in case someone with a Nabi SE can do a ROM dump.
Anyone?
Would you be able to flash the original room if your getting bootloops after putting twrp recovery on it?
Gigabuster said:
Would you be able to flash the original room if your getting bootloops after putting twrp recovery on it?
Click to expand...
Click to collapse
Yup, and it would be prudent for you to have made an SP Flash Tool backup of the SE first before you even mess with it.
Sorry to bother. My digitizer seems a little better after wipe with twrp, but now I am unable to get system to mount to install different ROM. I know there is a backup posted but I am unsure if that will work for the se. Also, if I can find it after moving I have a twrp backup I made of nabi se if it helps with any type of development
Q is will that backup suffice for the se nabi2? running 3.0 sw I believe... Thx in advance
remarkablecow913 said:
Sorry to bother. My digitizer seems a little better after wipe with twrp, but now I am unable to get system to mount to install different ROM. I know there is a backup posted but I am unsure if that will work for the se. Also, if I can find it after moving I have a twrp backup I made of nabi se if it helps with any type of development
Q is will that backup suffice for the se nabi2? running 3.0 sw I believe... Thx in advance
Click to expand...
Click to collapse
Try flashing system.img and boot from this backup I made using SP Flash Tool, or perhaps the Flash Image feature built into TWRP:
Code:
https://www.4shared.com/rar/UzxacJrUfi/NBTY07SMKG_160823_ForFlashtool.html
Nm. I was able to download. Thank you very much for the help.
blakegriplingph said:
Try flashing system.img and boot from this backup I made using SP Flash Tool, or perhaps the Flash Image feature built into TWRP:
Click to expand...
Click to collapse
remarkablecow913 said:
Nm. I was able to download. Thank you very much for the help.
Click to expand...
Click to collapse
You're welcome!
Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error