Argghhhhhh"!!!!
Can someone please help me out ASAP?.
I am so confused and mind boggled!.
I have a HUAWEI P10 (VTR-L09). I have a problem with the main camera, it is blurry. I tried everything to get it working apart from another rom/flash. I tried flashing stock UPDATE.APP rom to the phone but always got FAILED error!. So, Yesterday i spent literally ALL DAY unlocking the bootloader, rooting, installing TWRP/SU..etc. I looked at endless guides and tutorials, but links for certain software used are either dead or not relevant to my phone!. Eventually i got there.
Now i wanted to flash a rom, it seems every phone i own, every time i go to root and flash a rom to each phone the procedure is completely different and its getting ridiculously difficult now to do it (for me anyway).
I followed a procedure to turn the update.app into RECOVERY/SYSTEM/BOOT img files. I went into TWRP and flashed BOOT and RECOVERY. Now the phone wont boot up.
I am without a phone. Im mind boggled, after you've stopped laughing, can anyone please guide me????.
I no longer have the STOCK recovery... i am using TWRP. There's no damn rom flash files for my model phone on this forum!...that i can see!.
I am trying to ask on the huawei section, but it seems nobody is alive in there.
Help?
Don't panic.Breath.Breath Breath.
Now Listen(Not Laughing)You have Two options.
1:Ask a Guy(or every guy Just In case)On The TWRP forums To Backup Their Files and Upload Them for You.Then Create The exact same Folders and Replace Files And Flash It.Boom no harm Done No Apps deleted Stock Is on.
2)Flash Stock ROM.
3)Flash Custom ROM.
4)Ask a Guy at the TWRP forum To Backup and Upload Their Nand Backup.
5)Take a Brick Place the phone on It and Smash On It.
6)Try Using the stock Kernel and Boot Img From TWRP.It's Either In/dev or /data Or Somewhere With an Ending stock_system Img.Version blah blah blah.tar.gz
Unpack and Install.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
Don't panic.Breath.Breath Breath.
Now Listen(Not Laughing)You have Two options.
1:Ask a Guy(or every guy Just In case)On The TWRP forums To Backup Their Files and Upload Them for You.Then Create The exact same Folders and Replace Files And Flash It.Boom no harm Done No Apps deleted Stock Is on.
2)Flash Stock ROM.
3)Flash Custom ROM.
4)Ask a Guy at the TWRP forum To Backup and Upload Their Nand Backup.
5)Take a Brick Place the phone on It and Smash On It.
6)Try Using the stock Kernel and Boot Img From TWRP.It's Either In/dev or /data Or Somewhere With an Ending stock_system Img.Version blah blah blah.tar.gz
Unpack and Install.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
What is TWRP forums? where is it? do you have a link?. Please dumb everything down for me because i don't understand about recovery/flashing/roms/backups. I know nothing and i don't understand it (it is beyond my capabilities).
I made a massive mistake in doing what i have done so far without checking XDA for a custom rom for my phone. I just assumed it will exist, someone, somewhere has made one. But it seems they haven't.
It looks like this guide here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Will work for me. Only problem is, i literally do not understand it. I cannot follow that guide. If someone can help me remote support or something i would be for ever grateful...
Thanks
Ok.I am Going to Assume you have access to TWRP.Meaning you can Boot To It.Now the easiest thing is to flash a Custom ROM.So Here it Goes.Download This Named Update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1473/g104/v88287/f2/full/update.zip
Now Place The file on An SdCard.
Go to TWRP recovery and Press Install.Find a Folder named Storage.Click on It.Go To ExSdcard Or Some Strange Name Like B44BB-BHIF(This Is your SDcard Name).
After getting there find Your File(Named Update.zip).
Click it.
Wait for process to finish.
Reboot.
Done.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 12:27 PM ---------- Previous post was at 12:19 PM ----------
And Don't go Solo Bro.Never Go Solo.First Learn what Harm It can do.Then Make Backups In TWRP.
Save the backups Somewhere your phone Can't touch It Just in Case some Random Bug causes All Things to Get Loose.
Then do Whatever you Want but Never I repeat Never flash something ending with .Img.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
Ok.I am Going to Assume you have access to TWRP.Meaning you can Boot To It.Now the easiest thing is to flash a Custom ROM.So Here it Goes.Download This Named Update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1473/g104/v88287/f2/full/update.zip
Now Place The file on An SdCard.
Go to TWRP recovery and Press Install.Find a Folder named Storage.Click on It.Go To ExSdcard Or Some Strange Name Like B44BB-BHIF(This Is your SDcard Name).
After getting there find Your File(Named Update.zip).
Click it.
Wait for process to finish.
Reboot.
Done.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 12:27 PM ---------- Previous post was at 12:19 PM ----------
And Don't go Solo Bro.Never Go Solo.First Learn what Harm It can do.Then Make Backups In TWRP.
Save the backups Somewhere your phone Can't touch It Just in Case some Random Bug causes All Things to Get Loose.
Then do Whatever you Want but Never I repeat Never flash something ending with .Img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I did what you said sir, i get error ...
cHECK WRITE DATA TO PARTITION, WRITE DATA ERROR
UPDATE HUAWEI PKG FROM OTA ZIP: UPDATE PACKAGE FROM ZIP FAILED.
E:UNKNOWN COMMAND [ERRNO]
UPDATER PROCESS ENDED WITH ERROR: 9
ERROR INSTALLING ZIP FILE '/EXTERNAL_SD/UPDATE.ZIP"
I tried again after deleting dalvik...cache...etc..etc - no joy.
I tried again using fat32 micro sd - no joy.
Can you find anywhere on the internet a custom rom for VTR-L09? I am struggling. Its as if im the only one with the phone in the world.
I think Your Company is your enemy.because
*data partition is unusable due to the new file based encryption huawei applies via its software.
And I forget That to tell you despite using a Huawei Phone.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
I think Your Company is your enemy.because
*data partition is unusable due to the new file based encryption huawei applies via its software.
And I forget That to tell you despite using a Huawei Phone.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I have finally done it!.
Phew!. It is not easy!. Well its easy with this simple step by step guide. But not so easy following articles from XDA.
I followed these files and this guide:
http://www.stechguide.com/huawei-p10-b133-nougat-update/
Surprised no such info exists on XDA.
Unfortunately, after getting my phone back up and running again, my original problem still persists. That is the rear camera blurry in colour mode, but perfectly fine in black and white mode. The software refresh was my last resort since i've already physically changed the camera lens twice. I guess the phone is faulty, funny thing is other people have this same problem as mine.
You made your First Mistake While flashing TWRP.You didn't read the comments.The TWRP had a lethal Bug Called the Inability To cope with huawei's new S h hit Secuirity for /data partition.My method Could have worked If It hadn't for The Recovery Bug.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
You made your First Mistake While flashing TWRP.You didn't read the comments.The TWRP had a lethal Bug Called the Inability To cope with huawei's new S h hit Secuirity for /data partition.My method Could have worked If It hadn't for The Recovery Bug.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I used TWRP made for P10. I didn't use any old twrp....
I made sure compatibility first.
But thank you for spending the time to help me.
No.Look at Comments HE Said It is Not Fully Compatible.A Few Guys Got Nuked Due to Data partitions.He said That It was Unable to Write Data Partition.If you got yours From A Youtube or a Third party web or Channel That Idiot Clearly Ruined you
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
No.Look at Comments HE Said It is Not Fully Compatible.A Few Guys Got Nuked Due to Data partitions.He said That It was Unable to Write Data Partition.If you got yours From A Youtube or a Third party web or Channel That Idiot Clearly Ruined you
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I installed TWRP from XDA...
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
J4G3D said:
I installed TWRP from XDA...
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
Click to expand...
Click to collapse
Yes.See the bugs section.Data Partition Doesn't work Right now.
Sent from my Nexus 6P using Tapatalk
So, my phone is stickered as a Huawei H710VL. I guess Huawei uses an EMUI (?). When I tap "about phone," the EMUI logo is at the top, and at the very bottom it says, "custom version: CUSTC378D002."
I did not customize this myself.
How can I play around with changing my phone? I've been wanting to root it FOREVER but I can't seem to find anything online, and if I do, I'm too much of a confused noob to make it happen....
Help, please??
Related
After many lost hours of sleep, I finally give up and come to the community for help. I've seen the problems I'm having posted a lot, but I've not yet found a solution.
To start, all was well with my KitKat 4.4 ROM, except that my SIM would not read. So in my troubleshooting process, I did a full system wipe of everything through TWRP v2.6.3.0 (including internal memory), knowing that my ROM and other necessary files were saved on my SD card. The problem now is that TWRP will not show that I actually have an SD, so I'm stuck with no OS now. I've tried everything I've seen, such as formatting and properly "ejecting" the SD from my computer after doing so. I've tried three different SD cards, two 16gig and one 2 gig. Still won't read.
The only other thing I can think to do is use ADB to push or sideload - my device does not show at all when I try. Same result with fastboot. I'm suspecting that the issue with this is the driver. So far, after searching for hours and hours, the only driver I've found to use with the E970 is the usb_driver downloaded through SDK Manager. When I use this driver, it shows my phone as Google Galaxy Nexus ADB Interface in the Device Manager. But still no luck with ADB or Fastboot.
So I apologize if either of these has been solved one or more times before, but I'm desperate for help. Thanks!
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Rishi. said:
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Click to expand...
Click to collapse
As of right now, my phone has no ROM installed. I'd be willing to bet that it wouldn't read from an SD even before I tried my first ROM, but I don't really know since I never tried. Stupid on my part for not doing so before the wipe. I'll look into the modded TWRP, and hopefully it'll get me somewhere. Thanks for the help!
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Rishi. said:
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Click to expand...
Click to collapse
The problem with this is that I can't get ADB to find my device. If that were the case, I'd just push the ROM straight to my internal memory since that's the only one it sees. I've tried and double checked many times to make sure I was doing the ADB process properly. As far as I can tell, I am. Which leads me to think its not the proper driver for my phone. But I can't find any others.
I thought about LGNPST, but I can't get the phone into download mode without an OS. And that's the only way I know to use LGNPST.
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Rishi. said:
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Click to expand...
Click to collapse
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
SmithZ33 said:
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
Click to expand...
Click to collapse
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Rishi. said:
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Click to expand...
Click to collapse
Well, I opted to use LGNPST to flash TeenyBins and a TWRP that read my SD. Flashed the KitKat ROM just to try it, and it boots perfectly but I'm back to no SIM. So I'll be moving on to this new issue... haha
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Rishi. said:
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Haha, no I didn't. Between work and travel, I'm still trying to figure out this sim issue. It won't detect my sim on this ROM, or others it seems. I tried on a LiquidSmooth 4.3.1 ROM just now and it had the same issue. It's almost as if it has the detection set backwards. When I insert the sim, it thinks I've removed it and says ”sim removed." Then when removed, it says ”sim inserted” or something along those lines, and wants to restart. I'm at a loss, and I'm wondering why it could be doing this.
https://developers.google.com/android/nexus/images#mantarayktu84l
nigelhealy said:
https://developers.google.com/android/nexus/images#mantarayktu84l
Click to expand...
Click to collapse
does anyone know if it breaks root? if so, can we get root back in the same way?
jhnl33 said:
does anyone know if it breaks root? if so, can we get root back in the same way?
Click to expand...
Click to collapse
wait. I'm doing install now....
I'm just flashing the entire factory images. I never use my Nexus 10 anymore because the Wifi is a disaster... Worse that can happen is it actually works right now.. Which is highly doubtful.
---------- Post added at 07:37 PM ---------- Previous post was at 07:07 PM ----------
Still a broken POS... Installed, Play store restored all my stuff. Browsed around for a bit.. Sat it down... Went to the PC for 15 minutes.. Came back to Nexus 10.. First website I tried to open.. Yep.. No data throughput on two bars of wifi.. Same god damn crap that has plagued this stupid lemon of a tablet for ages.. Two bars of wifi strength and this stupid thing doesn't know what to do. Meanwhile my Nexus 4 performs flawlessly with 1 bar of wifi and never has data throughput issues since the day I bought it at launch.. Nexus 10 is such a massive flop...
nigelhealy said:
wait. I'm doing install now....
Click to expand...
Click to collapse
I did a stock install at command line. There is a bug which isn't relevant it tries to flash a recovery img which isn't included but I checked and its the most current version anyway.
Code:
fastboot flash bootloader ./bootloader-manta-mantamf01.img
error: cannot load './bootloader-manta-mantamf01.img': No such file or directory
fastboot -w update image-mantaray-ktu84l.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D104HJYB
--------------------------------------------
I then flashed CWM recovery, copied over supersu.zip, applied and then installed and used a root app (Stickmount) and it worked.
So.... far.... nothing broke.....
i did this first to my Nexus 10 as it has the simplest needs if I bricked it. Will do Nexus 7 then Nexus 5.
styckx said:
I'm just flashing the entire factory images. I never use my Nexus 10 anymore because the Wifi is a disaster... Worse that can happen is it actually works right now.. Which is highly doubtful.
---------- Post added at 07:37 PM ---------- Previous post was at 07:07 PM ----------
Still a broken POS... Installed, Play store restored all my stuff. Browsed around for a bit.. Sat it down... Went to the PC for 15 minutes.. Came back to Nexus 10.. First website I tried to open.. Yep.. No data throughput on two bars of wifi.. Same god damn crap that has plagued this stupid lemon of a tablet for ages.. Two bars of wifi strength and this stupid thing doesn't know what to do. Meanwhile my Nexus 4 performs flawlessly with 1 bar of wifi and never has data throughput issues since the day I bought it at launch.. Nexus 10 is such a massive flop...
Click to expand...
Click to collapse
Sell it. it's an issue with your router. I had the issue til I put on DD-WRT on my router and set a fixed channel, then it worked fine. Not saying don't blame N10, it should behave better, just if you all you are going to do is complain you're of nil value help.
styckx said:
I'm just flashing the entire factory images. I never use my Nexus 10 anymore because the Wifi is a disaster... Worse that can happen is it actually works right now.. Which is highly doubtful.
---------- Post added at 07:37 PM ---------- Previous post was at 07:07 PM ----------
Still a broken POS... Installed, Play store restored all my stuff. Browsed around for a bit.. Sat it down... Went to the PC for 15 minutes.. Came back to Nexus 10.. First website I tried to open.. Yep.. No data throughput on two bars of wifi.. Same god damn crap that has plagued this stupid lemon of a tablet for ages.. Two bars of wifi strength and this stupid thing doesn't know what to do. Meanwhile my Nexus 4 performs flawlessly with 1 bar of wifi and never has data throughput issues since the day I bought it at launch.. Nexus 10 is such a massive flop...
Click to expand...
Click to collapse
I had the exact same issue with the horrible wifi. It has been working flawlessly ever since I got it until about a month ago. On a 70 mbps connection with the router 2 feet away, I couldn't even load the play store, let alone anything else. I tried all that "disable wifi optimization" stuff and other things and nothing worked. 2 weeks ago, I relocked my bootloader and reverted everything back to stock and it still didn't work. Just for fun, I unlocked the bootloader again, still running stock, and magically my wifi is back to ~60 mbps and everything works perfectly again. I have absolutely no idea how. Maybe you should try it because you already factory reset it, try locking and unlocking the bootloader and see what happens. Good luck
---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------
nigelhealy said:
I did a stock install at command line. There is a bug which isn't relevant it tries to flash a recovery img which isn't included but I checked and its the most current version anyway.
I then flashed CWM recovery, copied over supersu.zip, applied and then installed and used a root app (Stickmount) and it worked.
So.... far.... nothing broke.....
Click to expand...
Click to collapse
Sweet thanks so much!!!
jhnl33 said:
does anyone know if it breaks root? if so, can we get root back in the same way?
Click to expand...
Click to collapse
FYI if you just run the flash-all script it erases everything, I actually prefer that to begin with a clean slate, but I know you can run a subset of comamnds to limit what is erases. So the method I did by definition breaks root, but getting it back is easy, just install custom recovery and copy the root zip and install in recovery.
So far... i'm configuring all my apps, nothing seems broke but it will take a while to know if any of my functions are broken....
Works
Root works.
Unlock, Flashed the Factory image, then CWM.img and then flashed SuperSU zip and everything is good.
I had a CWM backup so I'm up and running in no time.
BTW I have never ever had problems with WIFI, I have a netgear router, but it also works with trendnet and Linksys.
btw Total RAM is 1124832KB
First quadrant 2.0 is 5501 with stock kernel
I update thru OTA with superuser survival turned on. Confirmed it went perfectly fine on update with root still kept.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Fisrt problem... can't install busybox in /system/xbin due to lack of space in system partition...
I have TWRP installed on my Nexus 10. Can I simply boot into recovery and install the zip that's in the tarball? Or won't that work?
viccie said:
I have TWRP installed on my Nexus 10. Can I simply boot into recovery and install the zip that's in the tarball? Or won't that work?
Click to expand...
Click to collapse
No , it wont work. the file from google is in fact two .tar files inside each other. you need to decompress the first one , the second one has no extension ! add .tar extension to it and decompress it again. I used winrar to do it. you will get the batch file and rom zip file which requires fastboot to be installed. if you search on google you will find many guides on how to install factory images on nexus devices.
Edit : Well , I guess the google file is .tar.gz file and not two tar files inside eachother. but for an unknown reason when you download it the extension is .tar , I renamed it to .tar.gz and then decompressed it and it worked fine.
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
VivaErBetis said:
Fisrt problem... can't install busybox in /system/xbin due to lack of space in system partition...
Click to expand...
Click to collapse
I installed busybox with "BusyBox on Rails" app with no issues. it is working fine here.
where is bootloader img?
I extracted factory image file.
but i can not find bootloader img file.
I checked 'flash-all.sh' .
There is written like this 'fastboot flash bootloader bootloader-manta-mantamf01.img'
There have to be 'bootloader-manta-mantamf01.img'.
without updating new bootloader img, does it work well?
kun_ken said:
without updating new bootloader img, does it work well?
Click to expand...
Click to collapse
They forgot to include it in the factory image. But don't worry, it works well.
No TWRP flashable update.zip for 4.4.3 yet? Can't seem to find any on the threads, though folks are talking of OTA (I only see the factory image .tar).
VivaErBetis said:
Fisrt problem... can't install busybox in /system/xbin due to lack of space in system partition...
Click to expand...
Click to collapse
I just now installed it. Zero problems.
Of course i did what I always recommend of doign a full fresh flash and erase everything. It is always the safest best way. It took me about 30mins to install my apps and configure them.
ravenofdoom said:
No TWRP flashable update.zip for 4.4.3 yet? Can't seem to find any on the threads, though folks are talking of OTA (I only see the factory image .tar).
Click to expand...
Click to collapse
The URL of the OTA zip isn't out yet.
http://forum.xda-developers.com/showthread.php?t=1971165
http://forum.xda-developers.com/showpost.php?p=53108544&postcount=291
Wait or do what I always do and just do a full fresh install, it cleans out any crap.
Funny, the last 4.4.2 we had the OTA zips out before the full image zips, the reverse timing schedule. We had to do a flash then OTA for about a week i think then.
VivaErBetis said:
They forgot to include it in the factory image. But don't worry, it works well.
Click to expand...
Click to collapse
They forgot it but its also not necessary, the 4.4.2 had that same file flashed already.
nigelhealy said:
I just now installed it. Zero problems.
Of course i did what I always recommend of doign a full fresh flash and erase everything. It is always the safest best way. It took me about 30mins to install my apps and configure them.
Click to expand...
Click to collapse
Well, I finally installed the busybox applets using softlinks instead of copies. It may cause problems with some apps but it's the only way.
It's not a problem of fresh space but the system partition of the nexus 10 is really small compared to other nexus like 4 or 5.
LOOK http://bbs.gfan.com/forum.php?mod=viewthread&tid=7653470&pid=251597018&page=4&extra=#pid251597018
recovery 。。
http://pan.baidu.com/s/1eQjBXiq it work on my vs985 。
ROM
http://pan.baidu.com/s/1nt7Knd3
the recovery has some bugs。。。 but can work 。。。 we got roms now！！
so sorry for my English。。。
Anybody tried this, yet? I see it's an apk, so I wonder if it just emulates recovery.
wondering
spotmark said:
Anybody tried this, yet? I see it's an apk, so I wonder if it just emulates recovery.
Click to expand...
Click to collapse
I can't read the language....What does it say?
cairui505 said:
LOOK http://bbs.gfan.com/forum.php?mod=viewthread&tid=7653470&pid=251597018&page=4&extra=#pid251597018
recovery 。。
http://pan.baidu.com/s/1eQjBXiq it work on my vs985 。
ROM
http://pan.baidu.com/s/1nt7Knd3
the recovery has some bugs。。。 but can work 。。。 we got roms now！！
so sorry for my English。。。
Click to expand...
Click to collapse
Recovery does work I just got done making a backup and restoring it now. Excellent news if I do say so.
---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------
spotmark said:
Anybody tried this, yet? I see it's an apk, so I wonder if it just emulates recovery.
Click to expand...
Click to collapse
desireaftergod said:
I can't read the language....What does it say?
Click to expand...
Click to collapse
I couldn't read it either so I used Google Chrome and had Chrome translate it for me. Basically the recovery is an apk and there is a chinese rom. I have tried the recovery but I have NOT tried rom yet and not sure if I want too as everything will most likely be in chinese.
The recovery Failed to restore the backup it made. It gave the following error
E:format_volume failed to unmount "/system"
Error while formatting /system!
Always_Jonezen said:
Recovery does work I just got done making a backup and restoring it now. Excellent news if I do say so.
---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------
I couldn't read it either so I used Google Chrome and had Chrome translate it for me. Basically the recovery is an apk and there is a chinese rom. I have tried the recovery but I have NOT tried rom yet and not sure if I want too as everything will most likely be in chinese.
The recovery Failed to restore the backup it made. It gave the following error
E:format_volume failed to unmount "/system"
Error while formatting /system!
Click to expand...
Click to collapse
Thanks for being a "guinea pig"....and reporting back
desireaftergod said:
Thanks for being a "guinea pig"....and reporting back
Click to expand...
Click to collapse
Lol, NP, someone has got too
Not installing anything on my phone that is not at least blessed by the devs here.
It's a site where I can't read the language and the app does things that I have no clue about.
Risk it if you want, but if you end up with a dead device or spyware; don't say I didn't warn you.
it's Chinese rom . I have already flash the rom and worked well
I'm guessing this is probably the same thing as the Chinese recovery that was "discovered" a couple weeks after the phone was released, just being rediscovered. Even if it's something different, if it's an .APK it's more than likely a flash tool rather than a recovery, seeing how the bootloader hasn't been unlocked and all. Also pretty sure it was a Chinese user who posted the other "recovery" and said it worked well for all functions. I dunno about anyone else, but seeing how I'm on Verizon (in the USA) and speak English, I have no use for a "Chinese ROM." Hopefully this goes without saying, but as tech_head said if you try flashing this "ROM" don't expect to have a working G3 when you're done. :silly:
THEbigSWEEN said:
I'm guessing this is probably the same thing as the Chinese recovery that was "discovered" a couple weeks after the phone was released, just being rediscovered. Even if it's something different, if it's an .APK it's more than likely a flash tool rather than a recovery, seeing how the bootloader hasn't been unlocked and all. Also pretty sure it was a Chinese user who posted the other "recovery" and said it worked well for all functions. I dunno about anyone else, but seeing how I'm on Verizon (in the USA) and speak English, I have no use for a "Chinese ROM." Hopefully this goes without saying, but as tech_head said if you try flashing this "ROM" don't expect to have a working G3 when you're done. :silly:
Click to expand...
Click to collapse
may be U r right. I just post it here to see if someone can fix the problem.and the'' rom '' also have English language.. whatever I am not the guy who make this..
Hurray
This Rom works 100%! I'm on it right now after switching the language from Chinese back to English it is like a daily driver. We should get a dev to see this! Plus I translated the forum through Google chrome and it is a development forum for the vs985. EDIT: No Data and Random reboots only known issues.
hmmm. ill be looking into this later
I've been using this Chinese CWM bootstrap APK for the longest.... well really only a month because that's how long I've had my G3... I've used this in combination with the kitkat deodexer tool to create a deodexed stock rom which works perfectly.... This CWM is also useful in flashing general mods like the pure audio mod for instance also perfectly flashes (adds a nice volume boost as well).. HOWEVER, people are right to be sketchy about it. For one thing, I don't think this installs any spyware on your phone like some have suggested, but it's by no means a full proof recovery either... yes system backups work, but don't dare try to restore it by any means or you'll get an error after it wipes your system to begin restore, and then you'll have to flash back to stock. Also don't do anything stupid like try and flash TMobile roms to your Verizon G3, because even though it will allow you to flash it and say it completed successfully, you will be overwriting your kernel with an insecure kernel and you will not be able to boot your device up at all.... also if you do something this stupid, you will also block yourself from being able to flash back to stock because your phone will think it's a D851 and not a VS985... Finally, I'd also avoid flashing this Chinese rom... yeah it worked and booted for me, but I had no 4g... I'm sure that if you back up your apn settings beforehand, you'll be fine, but still I'd just avoid it. So long story short, use this recovery, but don't expect miracles from it. Devs should really look into decompiling this bootstrap apk and fixing the mount points, and then we'd have a full functioning tethered CWM.
zachariahpope said:
I've been using this Chinese CWM bootstrap APK for the longest.... well really only a month because that's how long I've had my G3... I've used this in combination with the kitkat deodexer tool to create a deodexed stock rom which works perfectly.... This CWM is also useful in flashing general mods like the pure audio mod for instance also perfectly flashes (adds a nice volume boost as well).. HOWEVER, people are right to be sketchy about it. For one thing, I don't think this installs any spyware on your phone like some have suggested, but it's by no means a full proof recovery either... yes system backups work, but don't dare try to restore it by any means or you'll get an error after it wipes your system to begin restore, and then you'll have to flash back to stock. Also don't do anything stupid like try and flash TMobile roms to your Verizon G3, because even though it will allow you to flash it and say it completed successfully, you will be overwriting your kernel with an insecure kernel and you will not be able to boot your device up at all.... also if you do something this stupid, you will also block yourself from being able to flash back to stock because your phone will think it's a D851 and not a VS985... Finally, I'd also avoid flashing this Chinese rom... yeah it worked and booted for me, but I had no 4g... I'm sure that if you back up your apn settings beforehand, you'll be fine, but still I'd just avoid it. So long story short, use this recovery, but don't expect miracles from it. Devs should really look into decompiling this bootstrap apk and fixing the mount points, and then we'd have a full functioning tethered CWM.
Click to expand...
Click to collapse
Do you think I could get a link to your rom?
Update guys a friend on xda is taking this apk apart and will as time permits see how it works,if it's beneficial to vs985,and most importantly make sure nothing is there that would cause harm to our devices..Stay tuned ,will update you guys if I have more info!
kdouvia said:
Do you think I could get a link to your rom?
Click to expand...
Click to collapse
Absolutely just flash this for a complete stock deodexed system and framework... Don't wipe data or do anything special in cwm, just install zip from storage. Here ya go https://mega.co.nz/#!7ZkTTArS!p9WLDNIatV5VU6gewbFKVSdFR88wzdPUDcgR6SRXjow
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
If you have any left over odex files in system, I probably didn't bother deodexing them as they are bloatware apps that got deleted.
Decompiling the app....
dabug123 said:
Update guys a friend on xda is taking this apk apart and will as time permits see how it works,if it's beneficial to vs985,and most importantly make sure nothing is there that would cause harm to our devices..Stay tuned ,will update you guys if I have more info!
Click to expand...
Click to collapse
And who is this friend if you don't mind me asking?[emoji13]
krazy_smokezalot said:
And who is this friend if you don't mind me asking?[emoji13]
Click to expand...
Click to collapse
I prefer not to say until something pans out ..I will say he said mount points look OK but that he does not trust the site the apk is coming from and wouldnt use do to that reason
zachariahpope said:
Absolutely just flash this for a complete stock deodexed system and framework... Don't wipe data or do anything special in cwm, just install zip from storage. Here ya go https://mega.co.nz/#!7ZkTTArS!p9WLDNIatV5VU6gewbFKVSdFR88wzdPUDcgR6SRXjow
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
If you have any left over odex files in system, I probably didn't bother deodexing them as they are bloatware apps that got deleted.
Click to expand...
Click to collapse
Install of your zip is working great except I'm missing the LG Keyboard.
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Solved: http://forum.xda-developers.com/showpost.php?p=61354553&postcount=14
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did you by any chance use any special image or was it a normal image from Google?
tarasmuz said:
Did you by any chance use any special image or was it a normal image from Google?
Click to expand...
Click to collapse
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure that the device is fine. I flashed images before and had no problems at all.
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
jd1639 said:
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
Click to expand...
Click to collapse
I've just restarted and closed all the programs, but it didn't help. Going to be trying and will post if I manage to make it work. Thanks for your help!
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
jd1639 said:
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
tarasmuz said:
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
Click to expand...
Click to collapse
Just tried another unarchiver - no difference.
tarasmuz said:
Just tried another unarchiver - no difference.
Click to expand...
Click to collapse
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on a Mac, so The Unarchiver and Archive Utility.
tarasmuz said:
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Click to expand...
Click to collapse
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
cam30era said:
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
Click to expand...
Click to collapse
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
tarasmuz said:
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
Click to expand...
Click to collapse
I'm glad this worked out for you.
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
p̶h̶o̶n̶e̶ ̶n̶o̶w̶ ̶s̶t̶u̶c̶k̶ ̶i̶n̶ ̶R̶U̶U̶ ̶m̶o̶d̶e̶ ̶w̶i̶t̶h̶
S̶E̶C̶U̶R̶I̶T̶Y̶ ̶F̶A̶I̶L̶!̶ ̶
R̶U̶U̶ ̶ ̶
h̶a̶v̶n̶t̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶i̶t̶ ̶y̶e̶t̶ ̶h̶a̶v̶e̶ ̶t̶o̶ ̶w̶a̶i̶t̶ ̶u̶n̶t̶i̶l̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶d̶i̶e̶s̶ ̶(̶t̶h̶a̶n̶k̶s̶)̶ ̶d̶o̶n̶t̶ ̶h̶a̶v̶e̶ ̶s̶c̶r̶e̶w̶d̶r̶i̶v̶e̶r̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶o̶u̶t̶,̶ ̶o̶t̶h̶e̶r̶s̶ ̶h̶a̶v̶e̶ ̶s̶a̶i̶d̶ ̶r̶e̶s̶t̶a̶r̶t̶i̶n̶g̶ ̶w̶o̶n̶t̶ ̶f̶i̶x̶ ̶i̶t̶
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do this??
update: can get back into TWRP not sure what i can do from here as i dont have an SD card reader to transfer files just a usb and a phone with no OS
Swaaz said:
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
phone now stuck in RUU mode with
SECURITY FAIL!
RUU
havnt been able to restart it yet have to wait until battery dies (thanks) dont have screwdriver to take battery out, others have said restarting wont fix it
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do any of this when my phone is stuck in RUU mode??
Click to expand...
Click to collapse
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
this worked, i must of given up at exactly 7 seconds lol
dumb question but with all these programs ive downloaded tonight ive just about given up
if i factory reset my phone in android recovery mode (not TWRP, the one with the 4 androids) on a phone that doesnt have an OS installed there isnt some miracle chance it would revert to stock rom would it? the only thing on my phone is TWRP and i was using CM12 before everything spiraled out of control
update - phone can access TWRP so im back to square one, i tried RUU i tried adb sideload and i also tried the folliwing programs
sdkmanager
SP flash tool (cant be used with htc)
windroid toolkit
USDDeview
ODIN
i just want to start over and try again but i cant seem to fix this
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
Hope you can figure it out
Sent from my Z988 using Tapatalk
---------- Post added at 06:37 AM ---------- Previous post was at 06:23 AM ----------
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
I don't really know adb very much as I haven't really had much experience with it.
Will probably be picking up a nexus 6 and rooting it since those are 100% stock Android and are easy to root and unbrick etc I will definitely be getting more experience with adb and root
Sent from my Z988 using Tapatalk
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Swaaz said:
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Click to expand...
Click to collapse
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Swaaz said:
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Click to expand...
Click to collapse
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
unfortunately nintendo apps have decided to label anyone with a bootloader unlocked as a filthy hacker and block access to their games
god forbid i upgrade my stock rom
That's why I try to have multiple devices to use
Sent from my Z988 using Tapatalk
bump
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Swaaz said:
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Click to expand...
Click to collapse
I don't think so...
Sent from my Z988 using Tapatalk
back to square one, new magisk update came out today which claims to not brick phones... still bricks mine
i guess thread closed. nobody here and every 2 hours i come into a different problem so ill just keep toying with it
if anyone cares, my current issue is that i cannot flash the current TWRP it always results in a bootloop im currently using an older build and ive been told that i need the newest TWRP for the newest magisk build