Search results

So, It didn't work with netcat, so I did the following: connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it. Then dd-ed the image to the data partition. When I rebooted the phone, it didn't ask for a pin code and the file and folders where...

So an update: I dumped the data and recovery partition. adb pull /dev/block/sda13 data_encrypted.img adb pull /dev/block/sde22 recovery.img 5494 KB/s (67108864 bytes in 11.927s) Next I wiped the data partition, phone started normally. I encrypted the phone again with the same pin code. Next...

I have an idea, but I don't know if is doable. I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img). Next I would wipe the phone completely, setup encryption with the same pincode. Next I would like to restore the old data, but I don't know how. I hope this...

So I tried a sideload of the factory images. Flashing is successfull, next I reboot the phone. It shows me the oneplus logo and reboots to recovery. I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.

Thx, I checked but not really my situation. I don't have the 999 users issue. I have made a screenshot of my /sdcard folder: * it seem that my picture is not comming through, so a link to it imgur Hopes this sheds some light. What I got from those threads: My backup was pretty large, 22GB. I...

So today I wanted to try something as I had issues with an app. I made a full nandroid backup with twrp. After setting up my phone and try the new app I wanted to restore to the old situation. When restoring I got the error createTarFork() process ended with ERROR: 255 After a reboot, no...

So I replaced the power board, but the issue unfortunately remains the same. Lower microphone is not working. Anyone have an idea on what it might be?

Hi, I replaced my screen today. I bought a full assembly with mid frame and screen included. Everything is working fine except the microphone. Speaker, thrill motor is working. When using speaker mode the upper mike is working. I checked all connections and reseated every flatcable, but no...

I was encrypted before and I am still encrypted. I don't understand that taking a backup renders the phone unusable. Restore fails with createTarFork() process ended with ERROR=255. I made a clean flash(and locked bootloader) as it is a requirement for the latest OOS due to the upgrade to oreo...

I decided to upgrade to the latest Oxygen OS yesterday. I had root, and TWRP Custom Recovery(3.2.1-0) and unlocked bootloader. I unrooted, relocked bootloader and installed the latest full zip from oxygen os. Then I unlocked bootloader and rerooted again and installed TWRP Recovery again...

I'm having problems with installing the gapps. I get the error Status 6 installation aborted when I'm on cwm 6.0.4.7 recovery. When using twrp I get a verification failed. Anyone an idea on how to solve this?

Ok, I found the cruelpit. it was the usb port board that was faulty. I ordered one from ebay because my port was broken, however it is missing something on the mic. original header ebay header The bad one doesn't have a black film over the speaker. I replaced the usb port from an other n4...

deleted.

I have the following problem: I have bought 2 nexus 4 and combined those two to 1 working N4. I'm getting complaints from people that they can't hear me to well. We I put it on speaker they can understand me perfectly. Would this be a hardware or software issue? I'm running...

I have tested it, and I can't get it to work properly. When I use the stable version, I have gsm signal, but I cannot make calls and have no wifi.(Disable sim pin otherwise It won't work at all) With the nightly I have no gsm signal at all, wifi starts scanning but doesn't find any wireless...

I had to revert to the previous version of the rom due to severe battery draining. I did a dalvik an cache format, but without a change in battery drain. It was android os that was consuming most of the battery. I noticed that the phone was also a lot hotter in standby than before.

I'm having problems with the play store. After a fresh install, everything works ok, after a week or so, I can't download/update apps. They error out with error 495. Did a complete wipe and reinstalled everything again, then ik works ok for a week or so, then the problems start again. Anyone...

Thx for the extra option. I have done a full wipe, and it's stable and smoother now.

Any posibility to enable spoofing on all apps as a standard? Or a way to enable it on all apps with a touch of a button? Running it for a week now. Had some crahes and not realy smooth. All of this without a full wipe, but will do this now and see how it changes.

This is realy great, thx. In the app, i understand on means giving the correct infomation to the program?

Which model do you have? If you have the 608, then you can do it yourself.

Same experience here. Must say it's the first JB rom that runs quite smooth on my device.

The ota for the mz608 is availlable: Blur_Version.0.281.4.MZ608.Retail.en.EU You can find it here here Please mirror it if you want.

Thanks for the files, I was able to fix my broken xoom 2 mz608

What do you mean with It doesn't stick? Can you get into the recovery menu? You could also do a oem lock and oem ulock again. Then reflash everything again (boot, system, recovery if needed).

working on a xoom 2 me HC

Indeed your's is the wrong model. I have found this also yesterday. I was able to unbrick mine ;). Thanks for all help

Hi Thanks for responding in the first place. First can you check with motocast(on your computer) if it see's the update. If so please install Process monitor. Next launch process monitor, then launch the setup until it would actually uprade your device. Next save the trace. From this trace you...

You didn't brick it by rooting it. I think you bricked it when you changed the framework.apk.( I'm in the same situation :( ) Next you flashed the sbf which caused your bootloader problem. The xyz finds a way to get a rootshell. Next it mounts the system RW and pushes the superuser.apk and...

Without root I don't think it will be possible. Unrooting is doable. In Dan's script you can use the first 2 stages to make /system rw(I don't remember if I had to do a remount) Then you can remove the Superuser.apk and busybox and your system is unrooted. Next execute fase 3 and your back to...

Nice they fixed m for free. If you have him back, can you dump the system partition ( if it is still on Honycomb) I would like to try to flash it to mine, if this fails, i'll return it too.

Can you check if you can do the update through motocast? That could be a solution. if you see the update through motocast, there could be a possibility that we can extract the full flashes.

If anyone happens to get the upgrade message via ota, please do not upgrade yet. If you can get the update via motocast, there is a posibility you can extract the flash files and help some people to unbrick there xoom. If you can get the update via motocast, please use process monitor to track...

Caution: You need to be sure you have the latin america version of you mz608, otherwise it is possible you brick it completely. Can you post a screenshot of your about phone section?

I'm affraid that it won't work :crying: We need a signed image to be able to flash. I think a dump won't contain the sig, but I hope I'm wrong. I think I have to send mine back to motorola :mad: Do you have backlight bleeding at yours? I have a spot where the light is bleeding from :mad:

This is done on a Xoom 2 ME(mz608) I had bricked my xoom and tryed to revive it. During the process I hoped to have booted an alternative boot img, but without success. Next I got the "ap fastboot flash mode s flash failure" after each reboot. To remove this error I dit the following: I...

I see it has faild to flash the boot_signed. Can you try to flash it manualy? just put the boot_signed.img in your fastboor directory and fastboot flash boot boot_signed.img See if that helps? the motoboot can be only 2 partitions: mbm or mbmloader. I would thing mbmloader?

a dmesg from my device The partition layout p1 (mbmloader) p2 (mbm) p3 (mbmbackup) p4 (cdt.bin) p5 (pds) p6 (utags) p7 (logo.bin) p8 (sp) p9 (devtree) p10 (devtree_backup) p11 (boot) p12 (recovery) p13 (cdrom) p14 (misc) p15 (cid) p16 (kpanic) p17 (system) p18 (cache) p19...

I think i have something: From ad shell dmesg > log.txt you can get the partition layout. You have mbmloader mbm and mbmbackup. One of these is the boot loader. So try to dump these files and fast boot flash hboot hboot.img could work. Dd if=/dev/mmcblkp0px of=/someplacewhereyoucanwrite/St.img...

Its is hard to find the flash files, ik think we need emea instead of latam. It think it would be possible to flash the hboot from a working model if you know which partition it is.

BTW do you still have the output somewhere of the installation? another thing we could try is: wait for the update that will arrive in Q3, try to extract the files from there and try to fastboot flash them;

If we would know the partition layout this could be possible. i have one from belgium, so it could be the same model. I don't know if the partition layout is the same as the 10". The problem could be the fact that we have a locked bootloader:(

I didn't try to flash anything yet. The only thing I have done is rooted the tablet. Isn't the hardware almost completely the same as the xoom 2 10"? I can open it up to see, but some tips on how to proceed are always welcome.

I hope that you are trying to flash the mz608 official fastbootfiles :P I think I went wrong with the flash of the fastboot files.(do you have the latin america edition? -latem stands for latin america) Otherwise you could probably have fixed it with pushing the original framework-res.apk. I...

Hi I have a 8.2 me edition tab with modelnumber mz608.(wifi 3G 16GB) Which rom do I need to take( is this umts_everest? thx

Thanks for the rom. I used untill version 2.0 because of a lot FC's. Now I'm on andromeadus, but I miss some of the tweaks. I hope you either keep it as a rom or an add-on, but a rom is probably more stable.

Hi I think i messed up my wildfire possibly badly. A accidentally flashed a hboot of my htc vision to my htc wildfire. with the following command: dd if=/data/local/hboot_7230_Vision_HEP_0.85.0005_101011.nb0 of=/dev/block/mmcblk0p18 after I did this I realized I made a mistake. First...

I'm also looking for someone that can order one for me and ship it to belgium. So if someone would like to help me?

Changed my radio to the 26.06.02.27_M and gps works now. Maybe you can add it to the starting post that gps doesn't work with the 26.03.02.26_M radio.

I can't get the gps to work. I can switch on the gps but can't see any satelites with copilot. No issues on GingerVillain 1.5 i'm on radio 26.3.02.26. Any clues?